>-----Original Message----- >From: Drozdetski, Stan A. [mailto:[email protected]] >Sent: Friday, March 30, 2012 11:52 AM >To: [email protected] >Subject: [DISCUSS] Bootstrap CSS customizations > >Marijan has kicked off the effort to introduce the >Bootstrap<http://twitter.github.com/bootstrap/> front-end framework to >Rave, and MITRE folks will try to help out with that. The promise is that >relying >on Bootstrap UI controls, layouts, and typography will a) make Rave look >better, and b) save us work on the frond-end side of things. > >Here's a question to the group: how would you like to customize Bootstrap's >CSS?
I think an important note is that the decision to use Bootstrap CAN be pulled out of downstream implementations in favor of their own styling. As I see it, we are trying to make Rave flexible so that implementers can use whatever parts of it make sense. If you want to simply layer on your own skin, then Boostrap offers easy mechanisms to do so; however, if you want to replace the whole UI in favor of something completely different, that is an option too. Long story short, the decision to go with Bootstrap for the Demo and simplest customization case seems to make sense to me, so long as we keep the door open for deeper customizations and flexible UI implementations. > >There are two main approaches: > >1) Using LESS. LESS is a CSS processor: you specify variables, compile the >.less file, and generate your CSS. That's how the core Bootstrap CSS files are >built (see a more involved >description<http://twitter.github.com/bootstrap/less.html>). This is a >"cleaner" way to do it (for instance, you would specify the link color once - >not >in a million style definitions), but has the overhead of learning/using LESS. As this is just for the demo & light customizations, I think LESS makes sense. It provides a robust way to build your own custom skin without having to override styles. I think Jose (if he is still hanging around), might have a more detailed perspective on this. > >2) Using the out-of-the-box Bootstrap files, and appending Rave >customizations in a separate stylesheet (which will override Bootstrap style >definitions). > >Personally, I'm leaning towards the LESS approach for the core - but that >doesn't preclude individual designers from using approach 2 if they choose. >Thoughts? Anyone has experience customizing Bootstrap one way or >another? > >Stan Drozdetski >MITRE
