Error
Rock’s page editor currently renders inside the same front-end context as the page content itself. Because the editor view is nested within the content being edited, custom stylesheets, JavaScript, Bootstrap versions, and jQuery-based libraries can conflict with the editor.
This creates a major limitation for building faster, more interactive websites in Rock. Modern public-facing sites often rely on optimized CSS, newer JavaScript patterns, animation libraries, interactive filtering, sliders, dynamic cards, responsive menus, and updated framework versions. However, because the editor shares the same rendering environment, these enhancements can slow down or disrupt the editing experience.
I am proposing that Rock’s CMS editor interface be compiled and rendered separately from the page content. The editor should have its own protected styles, scripts, layout, and dependencies instead of inheriting from or competing with the active website theme.
This would allow public-facing pages to use modern CSS, optimized JavaScript, updated Bootstrap versions, and interactive libraries without risking the stability or performance of the editor. The goal is to make Rock websites faster and more capable while keeping the content editing experience stable for staff.
Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.