Is your feature request related to a problem? Please describe.
Due to inconsistent development in the past between the main and lecture branches, there are discrepancies. Commits and updates have not always been applied to both branches. This has resulted in potential code divergence and unforeseen issues in both versions.
Describe the solution you'd like
A clear and thorough synchronization of the lecture branch with the main branch. This means:
- Comparing both branches and identifying missing or divergent commits.
- Ensuring all correct commits are present on both branches and resolving eventual conflicts.
- Attaching the relevant pull request(s) for the synchronization for documentation and review.
Describe alternatives you've considered
- Leaving the branches unsynchronized, which is risky and leads to further drift and maintenance complications.
- Only updating the most recent branch, which leads to loss of valuable changes.
Additional context
This issue is a sub-issue of #16, which is about modularizing institution-specific customizations. Thoroughly syncing the branches is a prerequisite for moving to a more modular approach and for future maintainability.
Is your feature request related to a problem? Please describe.
Due to inconsistent development in the past between the
mainandlecturebranches, there are discrepancies. Commits and updates have not always been applied to both branches. This has resulted in potential code divergence and unforeseen issues in both versions.Describe the solution you'd like
A clear and thorough synchronization of the
lecturebranch with themainbranch. This means:Describe alternatives you've considered
Additional context
This issue is a sub-issue of #16, which is about modularizing institution-specific customizations. Thoroughly syncing the branches is a prerequisite for moving to a more modular approach and for future maintainability.