Do you have to call your less file/css output somewhere then?
On Jan 29, 3:54 am, Alex Chamberlain <[email protected]> wrote: > There's a slightly better way... > > If you @include "boostrap.less" in your own less file, then put your fixes > underneath then you get a minimised css file to put in your html. > Furthermore, if anyone ever designed an optimising lessc, you get a free > optimisation. > > Alex > On 29 Jan 2012 10:06, "Abetam" <[email protected]> wrote: > > > > > > > > > 1) Load bootstrap.css > > > <link href="assets/css/bootstrap.css" rel="stylesheet" type="text/css" > > /> > > > 2) Load your fix.css > > > <link href="assets/css/bootstrap.fix.css" rel="stylesheet" > > type="text/css" /> > > > In your fix.css, you would have something like : > > > .tabs > li > a, .pills > li > a { > >> display: block; > >> text-decoration: none; > >> background-color: #eee; > >> border-color: #eee #eee #ddd; > >> } > >> body { > >> background-color: #fff; > >> background-image: none; > >> background-repeat: repeat-x; > >> padding-top: 0px; > >> } > >> .icon { > >> background-image: url(img/glyphicons-halflings.png); > >> } > >> .icon.white { > >> background-image: url(img/glyphicons-halflings-white.png); > >> } > >> body > .navbar-fixed-top .brand { > >> color: #0099cc; > >> } > > > this way, most of the time, you can grab the latest copy of bootstrap.css > > drop without worrying too much about messing with the original file.
