markdotto

As another commenter pointed out, you can recompile the .less files, excluding what you don't need. You can also use the web customizer in our hosted docs at getbootstrap.com.

Fellow GitHubber here :).

No, we don't use Jekyll for our blog. It's part of the GitHub.com codebase I believe.

For chat, all standard stuff really :). We use Campfire for group chat (dozens of rooms), Gtalk/AIM/etc for individual chats, and Skype or FaceTime for video chats.

Sorry, my typo made this more confusing. We never supported IE6. IE7 was supported through 2.3.2. With v3, we dropped IE7 and now support IE8+.

Yeah, sorry about those changes in the RCs. Really we used the wrong label and are sorry about that. All in all though, everything with those pre-releases worked out really well. Just a naming thing :).

And thank you! <3

v2.x supported IE7, so yeah. Since we dropped that we were able to make use of it.

Edit for typo

Yup, and we'll be working with these folks make this more official shortly. Stay tuned!

We do.

Naming changes were for consistency across the framework.

We only use `!important` on utilities where specificity would make them impractical. Quick floats, toggling by viewport size, etc make it necessary unfortunately. When it comes to every other component though, we don't use it at all.

Major version release enable us to break backward compatibility. Other motivations aside, I see no reason to not do it in attempts to do something better.

True, we could be louder about that. I'll get a tweet out about it shortly. To be honest I totally forgot about even mentioning it anywhere but in a few @ replies and issues on GitHub.

And once we add the theme, it'll become clear :).

Thanks for the feedback! <3

v3 will ship with a v2-ish theme that you can optionally enable.

Yeah we probably should have called them betas, but I'm fine with using RC—beta sounds way less serious and we want folks to just go to town on this. It's helped a lot.

And glad to hear you're a fan! <3

Super interesting—I did not realize that :). If you guys ever want to pass along feedback on how that went and what you did, please do! <3

Actually it is—it might behave perfectly right now, but the intent is that it is mobile-first and responsive like nearly every other component. If you're running into problems, let us know though via issues. <3

Awesome to hear, yo! <3