CMS back office

[schambon]

Create a simple back office to let administrators edit the content (and view missing translations) - ideally with a split-screen UI whereby content managers enter Markdown content and have a live rendition on a second pane.

[mkalam-alami]

Question: Is the backend supposed to support the same languages as the frontend? For the moment I've copy/pasted language code from the front app, if we have the same need I guess we could refactor such code to portal-core.

Also, in a development environment, running both Jettys at the same time will lead to issues (overriden cookies => CSRF errors) when browsing both apps through the same domain (e.g. localhost).

[schambon]

There's an enum of portal-supported constants in portal-core: OasisLocales. It's not very handy so could be refactored, but at least that's the full list of the languages we're supposed to support at present.

As per the other problem, I guess the easy way out is to use a reverse proxy, /etc/hosts and virtual hosts (so we can bind www.ozwillo.local to the portal and admin.ozwillo.local to the backoffice). That has the advantage of being very nearly the production configuration.

[mkalam-alami]

Done with the following limitations:

• The pages are currently on a single level, and the UI is not really scalable to support lots of pages.
• The "missing translations" badges are currently computed with a findAll() call (bad performance)
• No leverage of "th:fragment" to improve performance