Don't change the bootstrap core files (except bootstrap.less and variables.less), but keep an extra file (like style.less) with you own LESS and import bootstrap.less.
When you update, just keep bootstrap.less and variables.less, and add the new variables, On Thu, Sep 20, 2012 at 6:31 AM, Chris Geirman <[email protected]>wrote: > I don't know if this is a best practice. Hopefully someone else will chime > in with a better solution, but what I've done is kept track of > the customizations I've made in a text file along with the downloaded > bootstrap file. this way, I can apply those customizations again when > there's an upgrade. Here's a sample... > > >Colors > @blue: #5183CD > @green: #6C7B0C > @orange: #F46F1B > > >Navbar > @navbarHeight: 35px > @navbarBackground: @green > @navbarBackgroundHighlight: #8A9B0F > @navbarText: @white > @navbarLinkColor: @white > @navbarLinkColorHover: @white > @navbarLinkColorActive: @white > @navbarLinkBackgroundHover: #8A9B0F > @navbarLinkBackgroundActive: @navbarBackgroundHighlight > > >Dropdowns > @dropdownLinkBackgroundHover: @gray > > On Wednesday, September 19, 2012 4:00:55 PM UTC-7, jeff vankleeck wrote: >> >> What is the best practice for setting up a site that can be updated >> without losing all the mixins and changes. >> I did a site in 2.0.4 and what to keep it current (2.1)but I'm not sure >> which files to replace. >> Rookie questions, I know, but I'm new less and javascript stuff. >> >> thanks, >> jeff >> >> artgallery.calpoly.edu is the site. >> >
