Live data from Hacker News

Viewing profile — markdotto

markdotto

HN member
Joined
Mon, Mar 12, 2012, 10:20 PM UTC
HN karma
287
Public activity
54 items

About markdotto

Designer at GitHub, creator of Bootstrap. Previously designer at Twitter.

Recent public activity

  1. comment
    Comment #6742106

    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.

  2. comment
    Comment #6579131

    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 ch…

  3. comment
    Comment #6240329

    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+.

  4. comment
    Comment #6240076

    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. J…

  5. comment
    Comment #6240066

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

  6. comment
    Comment #6240059

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

  7. comment
  8. comment
    Comment #6210066

    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 si…

  9. comment
    Comment #6209868

    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 Git…

  10. comment
    Comment #6209813

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

  11. comment
    Comment #6209195

    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 t…

  12. comment
    Comment #6119413

    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

  13. comment
    Comment #6115867

    We've always used purple, save for the months of red in the v3 dev work that we then changed just a couple days ago. The purple was pulled directly from http://static.djbooth.net/p…

  14. comment
    Comment #6114645

    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…

  15. comment
    Comment #6112255

    Awesome to hear, yo! <3

  16. comment
    Comment #6112246

    Indeed there will be at least one more RC.

  17. comment
    Comment #6112244

    Thanks! And no, probably not—the two are most definitely not directly related.

  18. comment
    Comment #5559898

    Meh, I'm usually not one for variety :). The purple space background was designed by an illustrator here at GitHub and I just put it to use. That the page ended up being purple and…

  19. comment
    Comment #5559854

    I wrote all the styles for Bootstrap and refactored GitHub's forms and buttons a few months ago for a similar approach. Not 100% the same, but definitely close. All those styles ar…

  20. comment
    Comment #5188671

    All mobile first means is that instead of scaling CSS down for smaller devices, we start from there and work our way up instead. So far it's smarter defaults, little bit less code,…

  21. comment
    Comment #5186817

    Preference, readability, consistency with classes, better spell checking, etc. I always felt we should have done dashes instead, but shipping camelCase meant sticking with it for b…

  22. comment
    Comment #5186743

    It's on our list to check it out because of some of lack of control CSS transitions afford us. Hacks with overflow hidden cause issues, mobile performance is rather spotty, and mor…

  23. comment
    Comment #5186645

    I don't ever recall saying that, but if I did, I'm happy to have been wrong. Super stoked about the direction we're going.

  24. comment
    Comment #4945624

    Pretty much. Plus, it's a much better (and more socially known) metaphor for describing its function and presentation.

  25. comment
    Comment #4945618

    Negatory, but given the prominence of the ports and use of Sass, we'll likely try to do something here to help folks out who are using that over Less. No reason we couldn't write a…