Gutenberg publishing habits for busy SME teams
Short answer: Reusable blocks, patterns, and a simple style guide keep Gutenberg fast without every page becoming a one-off layout.
Teams that “just wing it” end with inconsistent headings, broken mobile stacks, and surprise spacing in NZ service pages.
Habits that scale
- Define allowed block patterns for common sections—hero, CTA, FAQ.
- Name reusable blocks clearly; delete unused ones quarterly.
- Preview mobile before publish on long pages.
Permissions
Limit who can switch to custom HTML blocks—paste errors break layouts and security.
Training
Short Loom videos beat fifty-page PDFs staff never open.
Frequently asked questions
Are classic editors dead?
Some sites still use classic plugins—plan migration if you are on borrowed time.
How do we keep design consistent?
Theme styles + patterns; avoid ad-hoc colours per post.