61–70 of 104 posts
I recently converted my blog to CSS grid. In the past I would have lazily used bootstrap as I've used that for over three years and know the grid inside out. It was a touch intimidating at first. No framework! But it is really quite expressive. It took me 12 lines of CSS to get a traditional blog layout that collapsed on mobiles.
What are the preferred solutions for people that are forced to support IE11? I've seen fallback CSS and JavaScript polyfills used.
Here's a simple approach: https://www.smashingmagazine.com/2017/06/building-production... "Rather than using fallbacks and shims to ensure a design and layout look the same across all browsers, we’d provide the mobile vertical single-column layout to all browsers and then serve up advanced functionality to those browsers and viewport widths that can take advantage of them."
A good way to bring a client round is to explain that the time saved on making IE11 pixel perfect is better spent adding features elsewhere.
Earlier quoted context omitted.
What I think goes unrecognized in the design community is what a tremendous skill it is to be able to put together really disparately styled and designed UX elements into a cohesive whole. Pre Bootstrap / Material / whatever - I'd end up with designs that were just incoherent. You'd look at a modal, or a file upload or something and none of them individually were that awful, but as a whole they didn't fit together.
How often can you use Bootstrap components unaltered? I'm either working on things where aesthetics are important enough that I'd have to write custom CSS for every component, or where aesthetics are so unimportant that stylistic coherence is irrelevant. When I use things like Bootstrap it's as a scaffolding in the early stages of development before I write enough of my own CSS. Eventually then I've restyled all the…
Can someone illuminate me as to what are some of the reasons that would make someone style with CSS Grid with a Fallback to Bootstrap? Considering you are already writing Bootstrap due to compatibility concerns why not just keep using that? I feel like adding another dependency like this would just create a risk of having design differences pop up over time. Mind you, I don't hate CSS Grid. I really enjoyed learning…
It's about time the web got a decent layout system. Every UI toolkit that I know of (wxWidgets, Tcl/Tk, Qt) has some form of layout mechanism (box layout, grid layout, etc), and they'd had it for years/decades. On the web though, people have been hacking around this omission for ages with tables and assorted "grid" systems (pure css, bootstrap, etc). The needs for layout management was there for as long as I can reme…
Because Web browsers originally operated under a document-focused paradigm rather than an application-focused paradigm. (The CSS box model spec makes much more sense if you dig through it with this in mind.) Even after Javascript came out, there wasn't really a notion of a Web application in the modern sense- if you wanted to deliver rich content, the primary way to do it was via Flash or Java applets. I would hazard…
Earlier quoted context omitted.
Because Web browsers originally operated under a document-focused paradigm rather than an application-focused paradigm. (The CSS box model spec makes much more sense if you dig through it with this in mind.) Even after Javascript came out, there wasn't really a notion of a Web application in the modern sense- if you wanted to deliver rich content, the primary way to do it was via Flash or Java applets. I would hazard…
The question is why it was deemed necessary to morph the document-centric Web into a Frankenplatform, and for what price. The complexity of CSS has already driven Opera (who once employed the original inventor of CSS) out of the business of producing a web renderer.
I recently converted my blog to CSS grid. In the past I would have lazily used bootstrap as I've used that for over three years and know the grid inside out. It was a touch intimidating at first. No framework! But it is really quite expressive. It took me 12 lines of CSS to get a traditional blog layout that collapsed on mobiles.
Do you have a link? I am thinking about converting my blog to CSS-Grid, but would like some inspiration.
Code here:
https://github.com/GrilloPress/grillopress.github.io?files=1
The idea behind my blog is every major article I style slightly differently.
Have an upcoming design kanban one where I've played about a bit more with grids to create the boards
It's about time the web got a decent layout system. Every UI toolkit that I know of (wxWidgets, Tcl/Tk, Qt) has some form of layout mechanism (box layout, grid layout, etc), and they'd had it for years/decades. On the web though, people have been hacking around this omission for ages with tables and assorted "grid" systems (pure css, bootstrap, etc). The needs for layout management was there for as long as I can reme…
Web development is just starting to catch up to where we were fifteen years ago. Things like type safety, unit testing, and dependency management are still fairly new on the Javascript side of the house, and I'd argue that Maven is lightyears ahead of NPM or pack or gulp or whatever the fuck the kids are using these days. The UI side is even worse. When you compare $todays_web_framework to QT or Swing, it's like drop…
Can someone illuminate me as to what are some of the reasons that would make someone style with CSS Grid with a Fallback to Bootstrap? Considering you are already writing Bootstrap due to compatibility concerns why not just keep using that? I feel like adding another dependency like this would just create a risk of having design differences pop up over time. Mind you, I don't hate CSS Grid. I really enjoyed learning…
> Can someone illuminate me as to what are some of the reasons that would make someone style with CSS Grid with a Fallback to Bootstrap? Generous interpretation: graceful upgrade when CSS grid has sufficient browser support. Realistic interpretation: to work with the 'new hot' and not the 'old stodgy'