Thank You Bootstrap 1
kylerego.github.io
Thank You Bootstrap 1
1–10 of 65 posts
Re: Thank You Bootstrap 1
#2Visually, bootstrap 2.23 was peak, before the flat bullshit took hold.
Re: Thank You Bootstrap 1
#3I clicked this totally expecting this to be somebody still using Bootstrap Version 1.0 haha
Re: Thank You Bootstrap 1
#4Visually, bootstrap 2.23 was peak, before the flat bullshit took hold.
I'm hearing I need to downgrade the Bootstrap in my suite? (A young addition).
Which is great because Bootstrap 2-3, whenever I used it, was pleasant.
I wasn't aware of the development timeline, thanks for the lead. Not flat is appealing.
I picked ExtJS 2.0.2 for a specific reason, seemingly rando old trusty version as base.
Re: Thank You Bootstrap 1
#5Visually, bootstrap 2.23 was peak, before the flat bullshit took hold.
Agreed.
You don't need a css framework to do a flat UI, just remove all of the borders from every element.
Re: Thank You Bootstrap 1
#6Visually, bootstrap 2.23 was peak, before the flat bullshit took hold.
Agreed. You don't need a css framework to do a flat UI, just remove all of the borders from every element.
http://web.archive.org/web/20120119042311/http://www.getskel... was also the peak.
Re: Thank You Bootstrap 1
#7Something that I've often wished, as a primarily backend focused engineer, often without frontend support, is for designers or perhaps design engineers, to pretty much build Bootstrap themes. That would let me code to the Bootstrap docs (which are pretty good), while allowing us to brand or customise whatever we're working on. I've seen even contract designers push back on this idea, suggesting that doing such a thing is beneath them, and I've heard frontend engineers push back on using Bootstrap as the framework.
This has always struck me as odd. From my, admittedly naive, point of view, Bootstrap seems to be a reasonable framework for customisation. I've done this myself in personal projects. It just doesn't seem like others see it as a design system framework in that way. Few teams have capacity to develop their own design systems, but a Bootstrap theme seems to be most of the benefits with not a lot of effort. That said, I've never been particularly enthused with third party Bootstrap themes, they seem to have too much custom work and lock-in.
What am I missing? I've not used Tailwind, but it seems like perhaps the goal of Tailwind is to do something similar?
Re: Thank You Bootstrap 1
#8Visually, bootstrap 2.23 was peak, before the flat bullshit took hold.
To be fair, a lot of people miss that Bootstrap is themeable, and what you are complaining about is just the default theme. E.g. check out https://bootswatch.com for examples, many aren't flatsville.
I've had confused conversations with UX, etc over the years when they say "We can't use Bootstrap - our colors are totally different!", etc.
Re: Thank You Bootstrap 1
#9I clicked this totally expecting this to be somebody still using Bootstrap Version 1.0 haha
I was expecting the same too. Somewhat disappointed now.
Re: Thank You Bootstrap 1
#10Something that I've often wished, as a primarily backend focused engineer, often without frontend support, is for designers or perhaps design engineers, to pretty much build Bootstrap themes. That would let me code to the Bootstrap docs (which are pretty good), while allowing us to brand or customise whatever we're working on. I've seen even contract designers push back on this idea, suggesting that doing such a thin…
Most companies will have a team building a component library which is equivalent.