Under the hood
Reminding myself that underneath it all is just HTML, CSS and JavaScript.
4 min read
Topics
- Front end
- Design systems
- Dependencies
- AI
TL;DR
- Rebuilding this site, I went back to a simple single-page style guide, like the ones I made in agencies.
- Since then, design systems have piled up abstractions and dependencies, and incidents like left-pad and Shai-Hulud show the cost.
- These tools solve real problems, but here I'm using the lowest level of abstraction that does the job.
- Underneath it all it's still HTML, CSS and JavaScript, and sometimes that's enough.
Rebuilding this website, I found myself doing something I hadn't done in years. Building an old-fashioned style guide.
Not a design system. Not a React component library with Storybook, documentation, versioning and a Figma counterpart.
Just a page. An inventory of the headings, buttons, layouts and all the little bits that make up the site.
It's been surprisingly refreshing, and got me thinking about how I ended up back here.
Making it work
I started building websites back in 2005, and I still remember many of the tricks we used to get a design looking just right across different browsers.
Cutting up Photoshop files and putting them back together in HTML was the day-to-day. Drafting sprite sheets, sliding-door backgrounds, images for rounded corners and fonts before @font-face — If you know, you know.
Working in an agency, jumping across projects and picking up other people's work meant we needed to find ways to make things quick consistent and understandable.
For me, this was a humble single-page style guide.
Much like Story book, it was a collection of every heading, button, form and component variation rendered in isolation. Powered by sensible CSS conventions, reusable templates and eventually approaches like BEM to keep things organised.
It wasn't particularly clever, it didn't need to be, it was all out of the box, low dependency and low tech.
Somewhere along the way
Twenty years later, I've spent a good part of my career standing up and maintaining sophisticated component libraries and design systems. I've know first-hand how impactful they can be when done right, particularly across larger teams and products.
However I've also watched us add abstraction upon abstraction, dependency upon dependency, libraries to manage libraries, tooling to manage the tooling and systems to support the systems.
I remind myself of left-pad, where in 2016, the tiny npm package was unpublished and broke builds across the JavaScript ecosystem. A few lines of code that was buried in dependency trees, caused widespread disruption.
A decade later, supply-chain attacks like Shai-Hulud have made those dependencies an even more serious consideration.
Now we have AI writing code, AI scanning for vulnerabilities and AI suggesting fixes. A machine-on-machine arms race, with developers caught in the middle reviewing pull requests from one machine to fix code written by another.
Watching the industry become inundated with this makes me want to let the bots fight it out and ask you to wake me when they're done, or perhaps its more like a spring clean...
I'm joking, well mostly... These tools are useful, and these established systems and libraries solve real problems. But there's something faintly ridiculous about the amount of machinery we've built to maintain all the other machinery. I keep hearing the words of an old mentor "keep it simple stupid".
Back where I started
In my previous post, I talked about moving from the things I need to the things I want.
Well, here's something I don't want. More complexity for the sake of it.
For this website, I'm finding myself quite happy keeping my head down, using the lowest level of abstraction that gets the job done.
HTML for structure, CSS for presentation, JavaScript where it's needed. A few templates and my trusty old style guide.
Browsers are considerably more capable than they were twenty years ago. We can do things natively now that once required all manner of workarounds in the past.
I'm not suggesting we abandon modern tooling or that the old ways were better. I certainly don't miss Internet Explorer or Netscape Navigator.
But it's nice to be reminded that underneath all those abstractions, it's still HTML, CSS and JavaScript.
And sometimes, that's enough.