Reduce documentation entropy

[EricBoix]

• Clarify/simplify the directory hierarchy
  Done in this issue
  RICT is about integrating components in order to deploy App (Demos). Thus RICT is not strictly about developing components but is more a cookbook : the directory hierarchy should reflect that. The keywords of the activity (to be used as directory names are): component use cases (illustrating a deployed usage of the component), demos, conception, integration, architecture, tools/tooling/tricks (e.g. use pgadmin, or shellscripts...). This includes

  • scatter/promote the Doc/Devel directory
  • SchellScripts content should be regroupted with Tools ?

• Merge the two inceptions

  • one
  • two

• Regroup DataLyonCityGML2009.md with the corresponding shellscript and avoid redundancy between the script and the markdown

• Regroup developer's related docs
  Sources

  • that
  • this
  • that again

• Missing doc: how to archiving branches ?
  Synthesize this and that

• [ ] Archive (refer above to the tool doc on the topic to be written) old branches of our py3dTiles fork. NOTE: how come the 3dtiles-temporal-v2 branch does not appear in the previous list ?

• Regroup the demos/how-tos/use-cases
  Similar sources

  • Doc/Process
  • how-to oriented demo install
  • UDV demos
  • Doc/Divers

• this documentation should be moved to 3DUSE

• Directories missing a Readme.md (what are they about?)

  • Doc/Itowns

• The Doc/Image directory should be scatered (or restructured). For example the Methodology_CityGML.md uses many of those images that are mixed up with other "articles"... Create a Methodology_CItyGML directory (actually this content should be in 3DUse but we are using it to talk about the structure of the documentation) rename Methodology_CityGML.md to Readme.md and move the attached image to Methodology_CItyGML /Images... In other terms adopt the structure of the WorkingWithLyonOpenData example.

• The following documents should be removed from RICT

  • this document
  • that document
  • this other document
  • the deprecated install: assert we are not loosing anything before

• what is the purpose of this WebGL_frameworks_game_engines survey ?

[jailln]

• Issues are scattered around software components (sometimes in RICT, sometimes in UDV or UDV-Server). What is the rule to determine where to put issues ?

[DiegoVinasco]

Moving this point to a new issue under the py3dtiles repo --> #7

• Archive (refer above to the tool doc on the topic to be written) old branches of our py3dTiles fork. NOTE: how come the 3dtiles-temporal-v2 branch does not appear in the previous list ?