What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== Currently, we can use CustomCSS to establish writer-built CSS for our content. It would be excellent if we could break it up into pieces, with each "chunk" of CSS for a given use case or kind of display artifact in its own page. Each time a change is saved to one, re-assemble the master CSS file that's actually used when content is rendered. What problems would this solve? =============================== This would make the CSS much easier to manage. In addition, once we have page editing permissions in place, we can give specific people or groups access to edit given CSS documents depending on their needs. This improves security, stability of the content, and usability in general. Who would use this? =================== All site admins. What would users see? ===================== CustomCSS would become a page that just lists all its sub-pages so we can get to them easily; otherwise, no visible changes to speak of. What would users do? What would happen as a result? =================================================== Editing of CSS would work the same way, just with many pieces instead of one huge file. Is there anything else we should know? ====================================== We could even move this out of the "Template" namespace and create a "CSS" or, perhaps better, "Styles" namespace.
we're trying to get rid of custome CSS, so this bug is invalid
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
Whiteboard: [specification][type:change] → [specification][type:change][triaged]
You need to log in before you can comment on or make changes to this bug.