Feature #1395

Individual content for frontends

Added by Alexander Watzinger 5 days ago. Updated 2 days ago.

In Progress
Target version:
Start date:
Estimated time:


We want to avoid Git branches for different frontends as long as possible. Current issue is the content 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).

  • 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 to admin/content
  • API: add functionality to get this content (with i18n)
  • Frontend: fetch and display intro and optional legal issue (with i18n)



Updated by Alexander Watzinger 2 days ago

  • Assignee set to Alexander Watzinger
  • Status changed from Acknowledged to In Progress
  • Description updated (diff)
  • Subject changed from Individual content without Git branches to Individual content for frontends

Talked with Christoph and looks like we go with the admin/backend option for text on start page. Adapted description and added optional legal issue content. This will be a combined effort between frontend, backend and API and we can discuss it Thursday. Not sure how to deal with the ticket (make 3 out of it?) but assigned it to myself for now.

Also available in: Atom PDF