On Mon, Feb 28, 2011 at 1:13 PM, rosslaird <r...@rosslaird.com> wrote: > My approach has been to place all css files in /css (and all > javascript in /js). I assume this folder will not be over-written by > future updates. These non-standard folders probably violate the > principle of convention over configuration, but the fact that the > folders are outside of /stylesheets and /javascripts -- and therefore > will not be messed with (I hope!) in future upgrades -- makes me more > comfortable.
The next version of Radiant will have a Sheets extension which allows you to better manage javascripts and stylesheets from the admin interface. By default it will use `css` and `js` but before the next version is released I'll be adding an option to change this. Regardless of that, if you have files in `/css` they will be chosen first before hitting the application. > > > > On Feb 27, 1:51 am, Mel <melforr...@gmail.com> wrote: >> You should make you style changes to admin/overrides.css so that they >> do not get written over by future updates. >> >> On Feb 27, 2:33 pm, BIO <bosbo...@alum.mit.edu> wrote: >> >> >> >> >> >> >> >> > No! I see admin/pages/styles now - this is too easy. >> >> > On Feb 26, 9:08 pm, BIO <bosbo...@alum.mit.edu> wrote: >> >> > > I'm new to Radiant and I've set up a site using the "styled blog" >> > > option (very nice, this Radiant). >> >> > > I'd like to change various colors and dimensions of the front page and >> > > at the top of the public/stylesheets/admin/overrides.css file I see >> > > that it says: >> >> > > "Make your custom overrides here. This file will not be updated by >> > > Radiant" >> >> > > Is this the right way? > -- Jim Gay Saturn Flyer LLC http://www.saturnflyer.com 571-403-0338
