What is the recommended deployment workflow for a customized Bulma build that maintains Flexbox compatibility and minimizes CSS size?

When preparing a production build of a website that uses Bulma, developers often need to adjust the framework’s design tokens (such as color, spacing, or breakpoints) to match a brand’s visual language while keeping the final stylesheet as small as possible and ensuring broad browser support.

The challenge lies in deciding whether to customize Bulma by overriding variables in the Sass source and then running a build step that includes Autoprefixer and possibly a CSS optimizer, or to rely on the pre‑compiled bulma.css from the CDN and apply additional stylesheets afterward. Uncertainties remain about how the build process affects the Flexbox‑based layout compatibility promised by Bulma’s autoprefixer usage and whether the resulting CSS retains the framework’s “environment agnostic” guarantee.

How can a team reliably produce a customized Bulma bundle for deployment? What build‑tool configuration preserves Bulma’s Flexbox compatibility? Which approach yields the smallest production‑ready CSS without breaking the framework’s core behavior?