Feature #1395
Updated by Alexander Watzinger over 3 years ago
We I want to avoid Git branches for different frontends as long as possible. Current possible because than it's easier to update, clearer if it's a main or develop version, ... First issue is would be the content text of the start page and an optional legal issue page. For this we will use the existing configuration functionality in the backend admin (tab content). Two options come to mind: *Advantages* *Configuration folder* Provide a default template which can be overridden in a custom folder which is not tracked in Git. *Configuration in backend* Advantages: * Update doesn't involve a manual Git pull or change on the server * Manager of the backend could change it themselves, which would be faster and less work for us * Easy to implement in backend because we already have this for e.g. backend intro, contact * Can be changed with an HTML editor * Multi language support * Easily expandable for other content e.g. contact, legal issues *To do* * Backend: Add frontend intro and legal issue options But for this to admin/content * API: add functionality work we also need to misuse the API or find another mechanism to get this content (with i18n) the text from the database. * Frontend: fetch I prefer the second option but your feedback and display intro and optional legal ideas are welcome, main aim is to have individual content without having to resort to Git branches. Next issue (with i18n) would be how to proceed about a custom logo but this should get it's own ticket.