Planning to upgrade to bootstrap 2? In Progress? Should I? about bootstrap.stylus HOT 4 OPEN

i think this project is defunct. which is unfortunately, bootstrap could be so much better in stylus

from bootstrap.stylus.

I keep thinking about ways to go about this. The way I see it, there are three:

1. Start with the LESS files. The concept of variables and mixins would be present, but honestly the level of rewrite would be enormous because Stylus can do things so much better, in ways that are fundamentally different than LESS.
2. Start with the generated CSS file. The initial port to Stylus would be as easy as > stylus --css bootstrap.css, and from there on out it would be numerous (and probably a high number of) passes at improvement. This would be great because it would free us from the ties to the LESS approach, but we would miss out on the benefits of Bootstrap's modularity. As a compromise though I guess the LESS modules could be closely referenced at each step.
3. Start from scratch. Stylus > LESS, and maybe trying to recreate something that was made with LESS is a flawed idea to begin with.

I was honestly originally hoping nib would head in the direction of Bootstrap (no offense, @visionmedia), and I just forked it the other day in hopes of adding a grid. I now think they serve different purposes... I still think nib should have a grid, but overall I believe nib is more behind-the-scenes crap, and the Stylus equivalent of Bootstrap will be more a visual library.

With my busy lack-of-time life, I am leaning toward # 2 and may start that effort up. I feel like the right way to do it though would be # 3, and it would be even better if @visionmedia started the project and it played nicely (but not tightly coupled) with nib.

Thoughts?

from bootstrap.stylus.

nib is nothing like bootstrap, it's the vendor layer. bootstrap is awesome in a lot of ways but personally I think it containing anything but structured styling is a big flaw, beyond cookie-cutter apps that is

from bootstrap.stylus.

Option # 3 it is.

I agree with the flaw you brought up. It's embarrassing as a front-end developer when I see big sites and apps that are shamelessly built with Bootstrap without any customization to speak of. I think the reason for this though is that many of the people who use Bootstrap are novice designers, and modifying the styles that come with Bootstrap has until recently required moderate CSS knowledge.

In a Stylus equivalent of Bootstrap, I wouldn't mind ignoring the people who just want a zero-customization cookie-cutter theme. However another part of me knows that Stylus is powerful enough to be a deadly designer-friendly combination of Bootstrap and jQueryUI where users can easily make/customize themes. I kind of cringe at any thought that involves the visual aspects of jQueryUI, but hopefully somebody knows where I was going with that comment.

This rant has little to do with this repository, and for that I apologize.

from bootstrap.stylus.