CDN playgrounds teach quickly; production needs a deliberate pipeline. Use this checklist before shipping Bulma to real users.
Production checklist
- Install via npm — pin
bulmaand compile from Sass when you need variable overrides - Trim CSS — import only needed partials or post-process unused rules; don’t ship full CDN weight if you use three components
- Document tokens — primary, link, radius, and font variables live in one SCSS entry file
- Wire interactive UI — navbar burger, tabs, modals: test keyboard flows and
aria-expandedupdates - Accessibility audit — contrast after theme overrides; visible focus on buttons and links
- CDN hygiene — if CDN remains, pin version and use SRI; prefer self-hosted CSS for compliance
- Conflict check — resolve clashes with SPA scoped styles or legacy global rules
Laravel teams often pair Bulma with Vite and a single SCSS entry—mirror the discipline you would apply to any CSS architecture decision.
Self-check
- Why is npm + Sass safer than an unpinned CDN at scale?
- Which interactive components did you keyboard-test?
- What breaks if you override variables only in compiled CSS instead of source SCSS?
Challenge
Ship checklist
- List two ways to customize Bulma (Sass vs CSS variables).
- Name one thing Bulma does not ship (unlike Bootstrap JS).
Done when: you can explain theming paths and the CSS-only trade-off.
Interview prep
- CDN vs Sass Bulma?
CDN for learning; Sass build to set variables before compile and import only needed components.