Our notes.
Short write-ups from actual projects — decisions we made, things that broke, and what we would do differently.
The website that didn't need a framework
Not every website needs React, Vue, or a full application behind it. Sometimes the best tool for a website is still HTML, CSS, and a little JavaScript.
read →Why websites get slow
Most slow websites don't become slow because of one dramatic mistake. They collect small decisions until the browser has far too much work to do.
read →WordPress doesn't have to be bloated
WordPress gets blamed for slow websites a lot. Usually the problem isn't WordPress itself, but everything that has been piled on top of it.
read →A design file isn't a website
Turning a Figma file into a real website is more than copying pixels. The browser has different rules, different constraints, and a lot more screen sizes to deal with.
read →You probably don't need to rebuild the website
A redesign can be useful, but rebuilding everything is not automatically the best way to fix a website. Sometimes a careful series of improvements is the better project.
read →When a website quietly becomes a web app
It often happens gradually: a login here, a dashboard there, a form that saves data, and suddenly the 'website' is doing application work.
read →