The Bootstrap folks released RC1 of version 3 on July 27, 2013. As I've perused the documentation, it's become clear that v3+ will incorporate some serious departures from earlier versions of the Bootstrap project, to the point that answers to pre-Bootstrap3 questions will not work in Bootstrap 3+.

For example, an inline unordered list previously mandated using the "inline" class: <ul class="inline">. Now that same styling requires the "list-inline" class: <ul class="list-inline">. The scaffolding nomenclature has changed from "spanX" to "col-X" (though it's even more complicated than that when you get into it, still, "span" is no more).

How should this be addressed? Is it time to "branch" the twitter-bootstrap tag?

Another issue to consider while we're addressing these tag names: the guys who develop Bootstrap no longer work for Twitter. So the 'twitter-' part of the tag (the part that used to distinguish it from the tag) is no longer applicable.

  • 1
    While twitter- might not be applicable anymore, it doesn't sound like bootstrap will be applicable either. Do you have a proposed replacement?
    – thegrinner
    Commented Aug 1, 2013 at 20:52
  • 2
    I don't understand why people keep saying that Bootstrap 3 has been released. I've been looking everywhere but all I find is a release candidate. They're even planning more than one RC, so it'll be a few weeks before Bootstrap 3 is actually released. Commented Aug 1, 2013 at 20:54
  • @BoltClock'saUnicorn I just checked the link, it explicitly says there will be more RCs: Today we're releasing the first of at least two release candidates for Bootstrap 3....
    – thegrinner
    Commented Aug 1, 2013 at 20:59
  • @thegrinner: no, I can't think of a single one that would work (besides "Bootstrap", which is already taken). :/ Commented Aug 2, 2013 at 2:48
  • 1
    @BoltClock'saUnicorn: are you implying that perhaps the changes in the class names are just temporary/only for the RC and that the actual release will revert the class names to the originals (I'm trying to understand why RC vs full-release should change the course of this discussion)? Commented Aug 2, 2013 at 2:51

1 Answer 1


I could rename to , for starters.

As for a tag specific to Bootstrap 3, seems awkwardly long but I'm just as uncertain about because it's still kind of "inconsistent" with the new name, if you know what I mean. Either way I would hold off on creating a version-specific tag at all until the community demonstrates a sufficient need for it.

And when that does happen, somebody else can create it easily and painlessly. Besides, I already have dibs on the original tag even though I've never used the framework at all ever since it was first released. I don't need or wish to be responsible for the creation of another Stack Overflow tag for a framework I don't use ;)

  • 1
    The rename to bootstrap-framework make sense to me, but I'm not convinced the new version merits a new tag. It still has a lot in common and I could point out other whole languages with API/ABI changes that have been more significant that aren't forked. Of course old answers are dated, but so are basic html/css/javascript questions.
    – Caleb
    Commented Aug 1, 2013 at 21:06

Not the answer you're looking for? Browse other questions tagged .