Currently we use a separate website branch to make deployments to our roster. We should ease this process as the website branch often has merge conflicts as menus bars etc. have conflicting changes.
Possible Implementation
Load a optional imprint.exs and only if this file is present, activate routes and make content accessible
Further Notes
Currently we use a separate website branch to make deployments to our roster. We should ease this process as the website branch often has merge conflicts as menus bars etc. have conflicting changes.
Possible Implementation
Checklist