cubicweb #4832808 Restructure the documentation [validation pending]

After quickly talking about it at the copil, here is the approximate
structure I propose for the documentation:
  • Narrative Documentation

    • book/*

      The current book, untouched at first.

  • Tutorials

  • API Documentation

    • api/*

      Systematic documentation of all the modules and all their members that needs to be known/understood by the cube developpers.

      Along with documenting the API, the corresponding parts of the book, the ones that tries to document the api, should be removed.

  • Changes

    • Quick access to the changelog
  • Developper Documentation

    • dev/
      • coding_standards
      • design docs
      • ...
prioritynormal
typebug
done in3.21.0
load left0.000
closed by<not specified>
patch[doc] small rst fixes and cleanups in changelog files [applied][doc] make the changelog chapter a one html page [applied][doc] reformat changes files headers [applied][doc] remove mentions of pyro and reposity instance type [applied][doc] put the tutorials between the intro and the `Repository development` toc of the book [applied][doc] move the documentations from docstring directly to the book. [applied][doc] more fixes of warnings/errors in doc build [applied][doc] fix warnings/errors in doc build [applied][doc] Start documenting the API [applied][doc] Remove useless indexes [applied][doc] Insert the dev docs in the toc [applied][doc] Restructure the documentation [applied][doc] Restructure the documentation [in-progress][doc] Start documenting the API [in-progress][doc] Remove useless indexes [in-progress][doc] Insert the dev docs in the toc [in-progress]