Bootstrap 3's 12-column grid, built on floats and a consistent gutter, has become our default starting point for early-stage prototypes this year. It's not what we ship in the final build for most projects - the visual language is recognisable and often needs stripping back - but for getting a clickable layout in front of a client fast, nothing beats it.
The grid in practice
<div class="row">
<div class="col-md-8">Main content</div>
<div class="col-md-4">Sidebar</div>
</div>
Know when to graduate off it
The trap is leaving Bootstrap's default classes and components in a final production build, where every site built with them starts to look the same. We treat it strictly as scaffolding: useful for the first draft, replaced with purpose-built CSS once the layout is approved.
What made Bootstrap 3 genuinely useful
The 12-column responsive grid, a consistent component library, and - critically - documentation good enough that a junior developer could ship a working layout on day one. For a studio taking on small-business sites with tight timelines, that combination mattered more than any individual component's design.
<div class="row">
<div class="col-md-8">Main content</div>
<div class="col-md-4">Sidebar</div>
</div>
The cost side of the trade
Every Bootstrap 3 site tends to look recognizably like a Bootstrap 3 site unless someone invests real time in overriding the defaults, and the framework's reliance on jQuery for its JavaScript components became a growing liability as the ecosystem moved away from it. It was the right tool for its moment - fast, consistent, well documented - and knowing when a project has outgrown "fast and consistent" into "needs its own design language" is the actual skill, not the framework choice itself.