markdotto

8 ms·

31.
by markdotto 14y ago
Yup, loving that we're getting rid of stuff out of the core. Definitely a major focal point of mine to date.
32.
by markdotto 14y ago
I struggled with making this decision, but ultimately it's all about readability for me. Hope it's not too much of a hassle for folks, but that's why this happens in a major update and not minor ones :).
33.
by markdotto 14y ago
I mentioned it before, but we didn't have an Octocat on the homepage before this.
34.
by markdotto 14y ago
The last version of our homepage never had an Octocat on it :).
35.
by markdotto 14y ago
It does use Sass, but was released after Bootstrap.
36.
by markdotto 14y ago
Later this week.
37.
by markdotto 14y ago
That's an understandable point of view, save for the waste of time part, but it's not the use case they're targeting (I think). Ratchet I feel is primarily for folks who don't use Interface Builder, who aren't engineers, and who just want t
38.
by markdotto 14y ago
Thanks for this! We're still waiting on a few changes before we do anything with hosting the old docs, so thanks for helping out in the interim :).
39.
by markdotto 14y ago
There should be no problems upgrading from 2.1.2 to 2.2.0—no features were removed and none had their classes changed.
40.
by markdotto 14y ago
Sorry for the bug on this one—we're aware of it and will try to push out a quick fix shortly. Thanks!
41.
by markdotto 14y ago
Mattia DMed me about this earlier today asking if it could be included in the Bootstrap core. For the time being, I've decided against it as it's another custom form element and we're not implementing anything like that at this point. That
42.
by markdotto 14y ago
Thanks man, appreciate that, and I hear you. I tried to maintain my cool and approach it as diplomatic and honestly as I could. This has been brewing for awhile and we have never responded, so I wanted to give as much context as possible. T
43.
by markdotto 14y ago
Hey Bryan, good to hear from you again. It's been roughly two years since we even spoke to each other, let alone saw each other in public. Before I dive into it, I have always and will continue to always have nothing but the best wishes for
44.
by markdotto 14y ago
Bootstrap creator here. tl;dr: <3, Jacob and I quit Twitter, he's going to Obvious, I'm going to GitHub, it's been amazing, nothing but love, Twitter is great, no ill will, Bootstrap is going to keep going, <3. First, thanks for the
45.
by markdotto 14y ago
No worries, and we appreciate you being fans :). Just wanted to let you know, and I figured you're attention would be here anyway.
46.
by markdotto 14y ago
Bootstrap creator here. * .navbar is for positioning/sizing. * .navbar-inner is required for the gradient because `overflow: visible;` is not respected by IE when `filter` is present. * .container is for centering the content within the nav
47.
by markdotto 14y ago
Thank you for calling this out. We'll fix it up as best as we can with the next release. Knew it going into this release it wasn't enough, so hopefully we can iterate on it to get the right behavior.
48.
by markdotto 14y ago
Yup, that was what we wanted to avoid for this round of updates. Cmd+F is your best friend in docs, no matter the format. Either way, we'll strive to improve as much as we can with future updates.
49.
by markdotto 14y ago
Come on, meow, I thought we were past this :).
50.
by markdotto 14y ago
For that release we had an upgrade guide. It wasn't the most complete, but I think it helped a lot. For this one, as is the case for every other release, just browse the tags and download the docs. Just as it's not terribly difficult for us
51.
by markdotto 14y ago
Yes! Absolutely. We wanted to add some javascript love to the dropdowns, but ultimately didn't have the time to get it in there for launch. The beautiful part of it is we can always improve :). Much love for the diagram as well—I'll see if
52.
by markdotto 14y ago
Fair criticism, but the subnav we had before, like the navbar, just doesn't scale. Let's less obtrusive, but hinders us in a big way. It's tough doing nav that works for everyone everywhere, but hopefully this pans out for us and folks usin
53.
by markdotto 14y ago
I actually pulled it at the last minute, but I was considering removing it for 2.1. Perhaps in 2.2 when we continue to evolve the docs :).
54.
by markdotto 15y ago
The fixed bottom navbar isn't documented yet, but we do have examples of the "dropup" menus in the dropdown buttons section here: http://twitter.github.com/bootstrap/components.html#buttonDr...