Skip to content
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

Team members unable to edit CMS pages with Hourglass theme #375

Open
mauromsl opened this issue May 21, 2024 · 0 comments
Open

Team members unable to edit CMS pages with Hourglass theme #375

mauromsl opened this issue May 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mauromsl
Copy link
Member

mauromsl commented May 21, 2024

Is your feature request related to a problem? Please describe.
Recently we've found frustration when our team are trying to expand the content on Janeway's CMS when running the hourglass theme.
Usually, one of our team members will request a change to be made, communicate the details of such change to developers and then someone from the technical team will need to produce a changeset via Github which then has to be reviewed and deployed. Use of django-components requires users to be able to access and run the django rendering backend, which is an open door for security vulnerabilites, as it allows for arbitrary code execution server side. Tailwind CSS would have not been a wise choice without a component library, so the trade-off that we made to run these technologies is now hindering usability of the platform long term.

This friction is a big departure from the WYSIWYG editor that made it possible for anyone in the team to edit content pages prior to running the theme

Describe the solution you'd like
To bring back the power to make edits to CMS pages to members of the team, we could write a custom template backend to limit the use of the backend engine only to delegate work to django-components. This mechanism would enable all users to alter the content that is provided to each component, however there wouldn't be a WYSIWYG interface for it, meaning users would be required to understand the inner workings of django-components or continue to delegate work to the tech team

Describe alternatives you've considered
An alternative would be to drop our CMS in favour of one provided from a vendor. Ideally, it would also support WYSIWYG and would probably require dropping django-components in favour of a solution that works natively with the CMS system itself.

Additional context
We've had a brief chat in Discord about this and agreed it makes sense to use an internal design meeting session to discuss this.

@mauromsl mauromsl added the enhancement New feature or request label May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant