Pairing Bricks with a utility CSS framework on a 50-page build

Pairing Bricks with a utility CSS framework on a 50-page build

We built a 50-page site in Bricks 1.9 using a utility-class framework (ACSS) instead of per-element styling. Goal: see if utility classes actually reduce output.

Measured against a prior per-element Bricks build:
— Generated CSS 210KB to 94KB after framework dedup
— Build time per page dropped ~30% once classes were memorized
— Consistent spacing scale killed pixel-pushing

Pros:
— Dramatically smaller, reusable stylesheet
— Spacing/typography stayed consistent for free

Cons:
— Steep learning curve; first week was slower
— Markup gets class-heavy and harder to skim

Best for: Bricks teams comfortable with utility-first CSS who want smaller output and design consistency at scale.