as an User, I want to get the log-in on landing page depending if backend reachable or not.
Also there should be a message board showing planned downtimes or long-term incident.

• heart-beat is implemented and binded to log-in (negative heart-beat = log-in option disabled)
• if planned downtimes addressed an information message is shown on the landing page
• if planned downtime or incident is active an information message is shown and log-in function is disabled

as a product owner I want a more transparent and simplified workflow process for continuous integration and continuous delivery. Also a clear API for (automated) continuous deployment is defined.

• CI for document-admins manageable and the workflow status transparent for all involved parties
• CD for document-admins manageable and the workflow status transparent for all involved parties

as the product owner I want are hard decoupling between middleware and frontend.

• Frontends shoud be independent and replaceable and primary developed with Angular

• all UI components are developed in Angular (admin UI optional with VUE or combined with Angualr/VUE)

• CI and Review process (for document admins) are transparency and the workflow status is clearly readable

• middleware API is well documented so customers are able to develop or enhance their UI themselves.

as a product owner, I want some fixed roles (page-admin, document-admin) and the option to define customer-based rolles with assignable groups and rights.

• page-admin can manage document-types, categories, and classifications
• page-admin can add, disable and reject/delete users
• page-admin can define roles and assign rights to roles
• document-admins can un-/assign roles to user
• document-admins can control CI and CD workflow of documents
• User can create, modify, delete, read documents depending on their roles and rights

as an product owner I want an API documentation for management and experts (developers), mainly in english and germans.
Managers should be able to high-level understand the interface and developers are able to implement and use it via https (TLS)

• API documentation in english is published to Github repository
• API documentation in german is published to Github repository
• routines / automatizations are documented in english and published to Github repository
• routines / automatizations are documented in german and published to Github repository

as a product owner I want digidocu is useable to create documentations and to publish for online reading and exports to PDF.

• IT-IS ReST API is up and running
• document types, classifications and catgories can be defined by page-admin
• User and roles can be created and assigned by page-admin
• User can register to digidocu, choose their timezone and change/reset their password
• Users can create, modify, delete and read articles based on their roles and rights; can assign classifications and categories
• Users can start the CI workflow of a document
• page-admin and user can print or create PDFs from document