CDN playgrounds teach quickly; production needs a deliberate build. Use this checklist before shipping Bootstrap to real users.
Production checklist
- Install via npm — import only the SCSS/JS modules you use, or compile a trimmed bundle
- Purge unused CSS — PurgeCSS or Bootstrap’s import partials; don’t ship the full 200KB+ if you need a sliver
- Pin versions — lock CDN or npm versions; document upgrade path for minor releases
- Customize tokens once — centralize brand colors and radii in Sass or CSS variables
- Accessibility audit — keyboard-test modals, dropdowns, and forms; verify contrast after theme overrides
- Conflict check — resolve clashes with framework-specific styles (React/Vue scoped CSS, legacy global rules)
- Security — use SRI hashes on CDN tags if CDN remains; prefer self-hosted assets for compliance
Laravel teams often pair Bootstrap with Vite and selective imports—mirror the discipline you would apply to any CSS architecture decision.
Self-check
- Why is npm + partial imports safer than a generic CDN link at scale?
- What breaks if you override variables in compiled CSS instead of source SCSS?
- Name two widgets you would keyboard-test before launch.
Challenge
Ship checklist
- List two ways to reduce CSS bundle size vs full CDN.
- Name one component that requires the JS bundle.
Done when: you can explain CDN vs npm build and which widgets need JS.
Interview prep
- CDN vs npm Bootstrap?
CDN for learning and prototypes; npm + Sass/build for theming, tree-shaking imports, and version pinning in production.