Disabled courses should be defined in the backend through a timestamp (for example). Frontend fetches these informations. Additionally we need conditional rendering on the Frontend course and topic page, so that it does not render if the course is not active (when the user enters a manual url).
Problem description
Possible approch
Acceptance criteria
Definition of Done
[ ] All acceptance criteria are met
[ ] The implementation of the User Story has been successfully accepted by the Product Owner
[ ] The implementation is in GitHub
[ ] A code review has been performed (or created in pairing program)
[ ] Code conventions are followed
[ ] Unit test coverage must be greater than 90%
[ ] All tests must have passed
[ ] Technical documentation created (Feature documented in GitHub Wiki)
[ ] UML class diagrams and component diagrams created and up-to-date
[ ] Documentation in realization created (source code)
[ ] Changelog created (Clear description in merge request)
Technical
Disabled courses should be defined in the backend through a timestamp (for example). Frontend fetches these informations. Additionally we need conditional rendering on the Frontend course and topic page, so that it does not render if the course is not active (when the user enters a manual url).
Problem description
Possible approch
Acceptance criteria
Definition of Done