Get the most from each lesson’s live editor with a deliberate loop—same habits that transfer to real Bulma projects.
Recommended workflow
- Read the concept section before touching code.
- Change one modifier group at a time (column sizes, then colors, then component variant).
- Resize the preview pane to test responsive behavior (
is-half-tablet,is-hidden-mobile). - Use browser DevTools to inspect which Bulma rule wins when debugging.
- Reset the editor if you drift too far from the lesson goal.
Review CSS cascade if custom CSS and Bulma helpers conflict—your overrides need equal or higher specificity, or Sass variables Bulma exposes at compile time.
Self-check
- Why change one modifier at a time during learning?
- What DevTools panel confirms a Bulma class is applied?
Challenge
CDN smoke test
- Add
button is-primaryin the playground. - Confirm styles load without any JavaScript file.
Done when: a styled Bulma button appears from CSS only.