Last week, a client site slowed me down again
At 10 p.m. Thursday, I was updating a booking page for a yoga studio in Hangzhou. Once I added the animation, interactions started stuttering. I refreshed seven or eight times, wishing I could just close the laptop. The client doesn’t code, and I didn’t want to spend most of my evenings debugging details. That’s the kind of friction Solid 2.0 is designed to address.
What it is, and who is already using it
Solid is an open-source frontend framework, and 2.0 is its latest major release. It doesn’t generate websites from thin air. Instead, when a page’s state changes, it updates only the affected parts rather than repeatedly redrawing entire sections. Think of it as patching a webpage locally instead of rebuilding it from scratch every time.
I know a designer, Chen Yu, who runs an independent portfolio in Shenzhen. He used Solid to build his portfolio site in March. Project filtering no longer flashes the entire page, and after delivery, he only has to maintain one set of page files. Still, he admits he got stuck at first: the official examples ran fine, but swapping them for his actual business threw errors. He eventually had to go back to the documentation and compare each section line by line.
What it costs to replicate today
Replicating a portfolio page with filtering: the software is free, and I’d expect 8–15 hours of work. The learning curve requires some HTML and CSS knowledge, plus the willingness to read example code line by line. You don’t need prior experience, but you can’t completely avoid error messages. The first step isn’t installing complicated software. It’s opening Solid’s official 2.0 starter example, clicking Start to run it in your browser, and following it to build a small button.
If you don’t currently have a technical colleague, this step alone could exceed your time budget. I’d rather practice with a small internal page first than take on a client order immediately. There’s no rush to try it, either: staying with familiar tools can still deliver the work.
How I’d approach it at each stage
Just starting: I’d build a practice page with only a heading, button, and form, keeping the budget to three hours. Once that works, I’d decide whether to continue rather than replacing my current site right away.
With one or two clients: I’d test it on a page that changes infrequently but has obvious interactions. I’d keep the old version as a fallback so revenue-generating projects aren’t affected.
Scaling up: I’d have a developer compare the same page’s speed and maintenance time in Solid and the current stack, then decide whether to add it to the standard workflow. I’d also write documentation the whole team can understand.