Public Facing
General
structure the documentation landing page: Documentation (developer, implementer, user)
Sandbox Landscape : near time status updates
Release Notes - Releases
Users
User documentation: http://docs.openimis.org/en/latest/ / http://docs.openimis.org/fr/latest/
which platform for user docs? readthedocs (current standard, but outdated)? gitbook? wiki?
Updated FAQ List
Outdated user documentation (Different Styles)
Implementers
Todo: Define Use Cases
Installation instructions: Installation and Country Localisation
Developers
List/structure of modules needs to be set up: refer to The JLN Process Matrix / JLN Process - OpenIMIS Mapping / https://docs.google.com/presentation/d/1eUqlOkK6MyTPZsQG3A8mZDzoIvFxzUtxi5r6UCVYYjc/edit#slide=id.g1192d288ca2_0_65 (slide 12)
Graphics: repository for architecture etc done with draw.io
release management - Definition of Done
step by step deliverables / check-list (integrate pull-requests, update doku, update modules overview)
GitHub-Documentation Redundancies
GitHub (Modules, Repositories?) → Remove/mark depreciated
Issues
youtube channel - how to keep it in synch with recent developments?
Hide Legacy as much as possible
Internal Documentation (under Maintenance Contract Project: 2020.T1 Maintenance )
Sandbox Server access / root account
keypass keyrings:
admin (on internal teams channel)
developers (on Google drive?)
GIZ internal
server contract login (keypass keyring)
DNS is still on cloudflare → Hetzner
web-page - wiki links: Incoming links from openIMIS.org