Hi Dan, folks,
That's it--I just wasn't quite sure how to explain it! :) How does one implement this for each? Is there an Apache config that I could use to point each library to a different style.css.tt2? I did a temporary fix yesterday by replacing a hard coded color in style.css.tt2 with a new option (directive?) which I then added to the colors.tt2 for a specific library, but this gets really messy really fast, especially if I have to do this for many libraries... Thanks again.... Tony On Wed, Nov 7, 2012 at 2:54 PM, Dan Scott <[email protected]> wrote: > On Wed, Nov 07, 2012 at 02:38:08PM -0500, Tony Bandy wrote: > > Hi all, > > > > I apologize in advance if this is the wrong list or it's been discussed > > already, but given 2.3 and the colors.tt2, is there a similar option for > > the regular stylesheet CSS? Can each library have their own version of > the > > stylesheet? Reason I'm asking is that given some of the colors are > > hard-coded in the sheet, with multiple libraries, not quite sure how to > > override this other than make new directives in each colors.tt2. > > I might not be understanding your question correctly, but > Open-ILS/src/templates/opac/css/style.css.tt2 is itself a template that > you could override at multiple levels (e.g. add one layer of > customization across the consortium, and then another layer at each > system, and then another layer at each branch). > > I know some people (hey bshum!) have expressed a want / need to break > the colors out more granularly, if there's some common ground that we > could find and merge to Evergreen core, that would probably help sites > with their customization efforts. > > If I'm misunderstanding, then some concrete examples would probably help > move the conversation along :) > -- Tony Bandy [email protected] OHIONET 1500 West Lane Ave. Columbus, OH 43221-3975 614-486-2966 x19
