Consolidated documentation portal `docs.itk.org`

[jcfr]

Description

This issue was created following discussion with @thewtex and @jadh4v.

It discusses the contents for a Sphinx-based website, published on the ReadTheDocs platform at https://docs.itk.org

Associated markdown and configuration would be organized in the folder Documentation/docs

Expected information

Table of content:

• About: Overview, Feature, License, Citing, History, Acknowledgments, Commercial Use ?, Contact US
• [ ] Getting Started
  • [x] Using Python
  • [ ] Using Jupyter: itkwidget, ...
  • [ ] Using Web Technology
  • [ ] Npm
  • [ ] Emscripten
  • [ ] WASM
  • [ ] WASI, ...
  • [ ] C++ and CMake
  • [ ] Using existing framework and applications
• [ ] Learning: Examles, Tutorials, ...
• [ ] Supported data formats
• [ ] Available Integrations: Napari, Matlab, VTK,
• [ ] Modules: List of ITK Modules including for each:
  • [ ] description & link to module specific README if any
  • [ ] icons linking to package specific documentation: Python, WASM, C++, ...
• [ ] API: Doxygen, bindgen, ...
• [ ] Developer`s Guide: These would include link to the ITK's Software Guide
• [ ] Resources
• [ ] Migrate old Wiki content:
  • [ ] Getting Started -
  • [ ] About - translate more up-to-date page itk.org/about to markdown -
  • [ ] FAQ - jhlegarreta PR #4308.
  • [ ] Mark Version control and releases wiki pages with {{ Historical }} -
  • [ ] Configuring and building -
  • [ ] Branches -
  • [ ] Doxygen Documentation - jhlegarreta PR #4314.
  • [ ] ITKDoxygen on GitHub
  • [ ] Dashboard Setup
  • [ ] Developer statistics (new system?)
  • [ ] Plugin IO mechanisms -
  • [ ] Open Science -
  • [ ] Other Software - jhlegarreta PR #4317.
  • [ ] MetaIO -
• [ ] Work on example issues

Additional Information

References:

• https://docs.vtk.org
• https://github.com/InsightSoftwareConsortium/ITKDoxygen

Related issues:

• https://github.com/InsightSoftwareConsortium/ITK/issues/4300
• https://github.com/InsightSoftwareConsortium/ITKDoxygen/issues/4

[jhlegarreta]

All shared links (e.g. SimpletITK, itk-wasm, etc.) should be put to a single document, and be included across all other Markdown files to ease maintenance.

[jhlegarreta]

Maybe we should already mark as deprecated those wiki pages that have been transferred and put a link to the new site so that

• users become increasingly aware of the new doc site,
• we void confusion,
• we have a better picture of what is left, and
• the community, including ourselves, has a clear evidence that the transition work is actually happening.