Why I Don't Use Bootstrap for Every Project

Why custom CSS still has a place when a framework is not the right fit.

Bootstrap is useful when its assumptions match the project, and rather less useful when the project spends its life arguing with them. I prefer to start with the problem in front of me and add a framework only when it saves more complexity than it introduces.

The useful question behind “Why I Don't Use Bootstrap for Every Project” is what changes in the work afterwards. A sound idea should improve a real decision, not only give us a neat phrase for describing it.

This matters because small choices repeat. What feels harmless once can quietly become the normal way of working.

Prefer the thing that survives contact

Front-end work has a habit of looking simple from a distance. The browser then introduces real content, small screens, old devices, keyboard navigation and somebody using the product in a way nobody drew in the design file.

That is why I favour choices that are easy to inspect. Start with semantic HTML, let CSS do the layout work it was designed for, and add JavaScript where it creates genuine value. Cleverness is occasionally useful; legibility is useful every day.

The best front-end code does not show off. It makes the interface feel obvious.

A practical way to start

Before changing anything, I try to answer three ordinary questions:

• Is the simpler option genuinely insufficient?
• Can somebody new explain the decision back to us?
• Have we left a safe and affordable route to revise it?

None of those questions produces an automatic answer. They do make the trade-offs visible, which is usually the point where a team can stop arguing from instinct and start making a decision together.

The web is wonderfully forgiving, but users should not have to rely on that forgiveness. Build from sturdy foundations and the interesting parts become much easier to enjoy.

The details will change from project to project. The underlying habit of paying attention travels well.