> I've been sensing the need for this as well. Mainly, it seems like only > people with developer privileges should be allowed to edit the > stylesheets. In this case it makes sense to put them on a styles tab > which is only showing when you have developer privileges.
Not necessarily, while the primary stylesheets, scripts, etc that govern the entire site should only be editable by developers, it would make sense to have stylesheets that only govern a specific elements in a set of pages (or even a single page) be editable by non-developer users groups, or even a specific user. While a page-by-page permission system for users would be too complex to be practical, there are times where stylesheets should not be restricted to developers. I'd suggest a global assets section which might require developer privileges and non-global assets which includes attachments, but isn't limited to them. This doesn't pertain specifically to assets, but following this stream of thought there should probably be a way to make assets cached indefinently. After all, once a website design is complete, I really doubt the stylesheets and scripts are going to be edited that often. It might be nice to have a way to save specific documents statically. This might not just pertain to assets though, It might make sense to allow users to have a choice to make pages without dynamic content to be cached for a longer period of time or served statically. This would be extremely useful if someone has a static page with high traffic by cutting down on the number of database queries, and processing time. I'm currently wishing I was better at scripting and programming. I'm a logician dammit! I can look at the code and understand what's happening but write it? Dear goodness, no. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
