...
- Dedicated page for each module under openIMIS Modules (with Page Properties, descriptions/basic explaination, version history - Based on release notes pages?)
- Clarify wording module / component / repository - Define and document for example “Claim AI” from different perspectives - “Claim AI” Module contains the Components “Claim AI BE” and “Claim AI FE” “?
- openIMIS Feature: One-Click-Installation with selection of modules instead of installing components one by one / Define Standard-Installation
- Rethink grouping of Components on Release 2022-04 according to Modules ->
- Include repository info instead of redundancy (and info gaps) between Release notes and repositories on GitHub (PlugIn?)
- Clarify usage of Pypi.org and npmjs.org with GitHub (calcrule links to GitHub, others to PyPi)
- Update Installation Guides (Docker and Non-Docker)
- Dependency Graph for modules / consistent dependency information in Sources Release 2022-04
- Reevaluate “Testing openIMIS” on Sources Release 2022-04
- Consider “Legacy” modules as “Deprecated” on Sources Release 2022-04
- Sort components by name on Sources Release 2022-04?
- Release 2022-04 Reevaluate redundant information in “Highlights” and “Release Notes”
- Combine Releases / Release 2022-04 , Release notes and Sources/Sources Release 2022-04 to reduce structural redunancy and confusion
- Clarify wording redundancy “openIMIS …” for components, modules, wiki pages, etc.