-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMS back office #1
Comments
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). |
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. |
Done with the following limitations:
|
- Remove and migrate uses of Authority model class (duplicate) - Remove unused code
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.
The text was updated successfully, but these errors were encountered: