You're editing the minified CSS!? I'm obviously a little biased here, but Kickstrap is the way to go. The entire Bootstrap library is kept completely unchanged in a separate folder while you write your customization on top of it. On my machine, I just made the Bootstrap folder in Kickstrap a git clone of the Bootstrap repo to update it every time I build my project.
And, since Django's beauty is in its modularization, Kickstrap and Django get along very well. I've seen a lot of people using it for Django, even though it can be used with virtually anything. One more thing, unlike just using straight Bootstrap, even with their "extend" instructions, with Kickstrap you can toggle on or off each Bootstrap component to keep your CSS small. For example, if you're not using button groups, you would just comment out //@import "...button-groups.less" and you can always turn it back on if you decide to use it later. With the apps, themes, and extensions store I'm building now (in Django), you'll also have access to all that. On Sunday, September 30, 2012 2:42:42 PM UTC-4, Dave wrote: > > Massimo et al, > > I wonder if it would be a good idea to look at building .less styles for > the welcome scaffolding. That could allow for easier customization of the > app. While I love Twitter bootstrap, it's quite a pain in the rear to edit > the minified CSS. Also, its beta, but I am doing some tinkering with > Kickstrap. It has some promise and neat features on top of bootstrap, > while maintaining full support for all bootstrap features. > > Thoughts? > --
