Hi Niv! Thanks so much for your thoughts. I have a Lynda.com account and will check out that course... after my Cinema 4D, SpeedGrade classes, etc, etc. :) !!
I'm really tempted to go down the LESS route. The main challenge I see is that then the customization will be in LESS class/source files and not in classic CSS. This could be a deal breaker for the client as they may want to apply said default style sheets to other none LESS projects. I'll have to ponder this a bit. Your enthusiasm as well as other from peers make me want to jump in. I hope I will get to soon!. Thanks again! Rich *Richard A. Price* Experience Architect, Richard Price Design Video & Motion Designer, Ascend Interactive [email protected] [email protected] Skype: RichardAPrice Twitter: @RichExperiences 303 263 1876 [image: View Richard Price's profile on LinkedIn] On Thu, Jun 27, 2013 at 5:04 PM, Niv Froehlich <[email protected]> wrote: > Hi Richard, > > YES! There are great reasons not to go pure CSS. LESS is a much better, > more efficient and more orderly way to use style sheets. You'll want to > output to to CSS for production, but develop using LESS. > > There is a great LESS course on lynda.com and you get a one week free > trial - you can be up and running and up to speed with LESS in couple of > hours, including using a great free and open-source IDE (Aptana Studio 3) > and LESS compiler (SIMPLess) - all covered in the course - you'll see the > advantages once you get going - and you'll never look back! > > In terms of over-riding id's and classes, consider that there are lots of > libraries of interface components built on Bootstrap (and lots more > coming!!!), so the closer you stick to Bootstrap's classes and id's (and > native LESS style sheets - changing only the 'constants/variables' to suit > your styling needs) the more 'modular' or 'portable' your GUI components > will be and the more you'll be able to utilize Bootstrap GUI components > used and created by others - that should essentially 'plug right in' - if > you go off the beaten path and utilize your own classes and id's - then you > potentially sacrifice these advantages to some degree. > > If you've heard of Joomla! the Joomla! project has standardized on > Bootstrap to help facilitate this process amongst thousands of contributing > component developers - you can read a bit about that effort at > http://jui.kyleledbetter.com/bootstrap. The idea behind the Joomla User > Interface Library (JUIL) is so that developers around the world have a > 'standard' to follow when it comes to styles sheets, classes, id's etc. so > that the GUI components they develop will 'plug right in' and provide a > consistent 'look and feel' with components developed by others. > > That said - once you know the advantages and disadvantages, feel free to > customize to suit your needs - keeping the above mind. > > Hope that helps! > > Niv > > > On Thu, Jun 27, 2013 at 4:49 PM, Richard Price > <[email protected]>wrote: > >> Hello all - >> >> I'm part way into customizing a sample micro-site's look and feel by >> simply overriding certain ids and classes from bootstrap.css in a simple >> set of added css files. >> >> Is this an okay route to go? It dawned on me that maybe I really should >> be using LESS, but what my client really would like is a set of abstracted >> (as much as possible) style sheets with standard declarations that are as >> easy for a Dev to snag and use in other projects as it is for PM's to peak >> in to and view colors, or margins, etc. >> >> So, bottom line, is there any big reason to not go the pure CSS path? I'd >> hate to create a huge mess that possibly won't even be able to affect BS in >> robust ways. >> >> Thanks much! >> Rich >> >> -- >> You received this message because you are subscribed to the Google Groups >> "twitter-bootstrap" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "twitter-bootstrap" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/twitter-bootstrap/4uz9-Iz3gZE/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "twitter-bootstrap" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
