3 ms·
Looking at your source code, any reason you're doing hand-rolled css, layouts, scrollable divs with main content, inline css? I remember doing this 15 years ag
by HatchedLake721 5y ago
Looking at your source code, any reason you're doing hand-rolled css, layouts, scrollable divs with main content, inline css?
I remember doing this 15 years ago.
Today this is a problem that was solved dozens of times, from Bootstrap, to Zurb and Tailwind - with productivity, accessibility and variety of devices and screen-sizes in mind.
Your website is unpleasant to use and scroll. It feels you're reinventing the wheel just for the sake of it?
- netr0ute 5y agoI make my website hand-made too, but because I found those tools to take too long to set up exactly how I want or they're too bulky.
- deleted 5y ago[deleted]
- andrewzah 5y agoI write my own css for my statically generated website (andrewzah.com). The problem with bootstrap etc is exactly that they’re aimed at being generic. They’re not specific enough to do what I want quite how I want it… and there’s the burden of learning them. It’s a lot easier to start with a good, semantic html structure and come up with exactly the CSS that one needs, rather than continually fight a system aimed at no one in particular. Not to mention the bloat of unnecessary CSS/JS that you don’t actually need.