Gutenberg is WordPress' native block editor. Full Site Editing (FSE) lets you edit the entire theme from the admin panel. But FSE pure isn't always ideal: complexity, learning curve, governance challenges. The smart approach? Combine the best: Gutenberg for content, Kadence or GreenShift as stable base, custom blocks where needed.
Why Gutenberg & Custom Blocks Matter
- Modularity: Reusable, versioned blocks, easy to extend.
- Semantics: Pure HTML5, accessible, search-engine friendly.
- Performance: Zero builder bloat, CSS tied to used blocks only.
- Governance: Full control over which blocks editors can use.
- Maintainability: Clean code, no lock-in to third-party builders.
Practical Approaches: FSE vs Kadence vs GreenShift
There's no absolute winner. I choose based on your needs:
FSE Pure (Full Site Editing)
Pros: Maximum freedom, minimal bloat, integrated theme editor, block theme that evolves with WordPress.
Cons: Steep learning curve, ecosystem still fragile, fewer pre-built templates.
Best for: Small-to-medium agencies managing few sites, tech-savvy teams, projects with development time.
Kadence (Hybrid Approach)
Pros: Premium theme + integrated builder, intuitive panel, block theme + graphical editor, good documentation.
Cons: Vendor dependence, learning curve for their UI, monthly/annual cost.
Best for: Agencies serving clients who want editor UI, fast projects, clients who edit frequently.
GreenShift (Advanced Block Builder)
Pros: Extremely powerful, advanced blocks with real-time logic, exceptional performance, no builder bloat, active community.
Cons: Steeper learning curve, cost, requires Gutenberg knowledge.
Best for: Agencies with complex projects, clients wanting advanced design without bloat, performance priority.
When to Choose Which
| Requirement | FSE Pure | Kadence | GreenShift |
|---|---|---|---|
| Performance | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Editor Ease | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ |
| Design Complexity | ⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| No Vendor Lock-in | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Learning Curve | ⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐ |
Custom Blocks & Patterns
Whether you choose FSE, Kadence, or GreenShift, custom blocks are the real value:
- Brand-specific blocks: CTA with company colors, testimonial cards, team grids.
- Reusable patterns: Hero + CTA, Feature grid + text, Image + overlay (pre-assembled block combinations).
- Editor-side logic: Custom attributes, validations, live preview.
- Data integration: Block showing latest posts/products/team from custom query.
Design System & Governance
For agencies, keeping the design system consistent is critical:
- Global tokens: Colors, spacing, typography defined in theme.json.
- Block allowlist: Disable unnecessary blocks, show only approved ones.
- Presets & templates: Hero page, gallery page, blog index pre-built.
- Editor documentation: Guide on how to use custom blocks.
SEO & Accessibility Built-In
Native Gutenberg means:
- Semantic HTML: Heading, list, nav natively correct.
- Accessibility: Focus states, keyboard navigation, ARIA native in Gutenberg.
- Schema markup: Built into blocks (article, organization, FAQ schema).
- Core Web Vitals: Zero builder bloat = natural performance.
Agency Workflow
1. Design System Audit
I analyze your Figma design system, extract color tokens, spacing, typography rules.
2. Theme Setup
Setup: theme.json with global tokens, block editor CSS, block patterns, allowlist.
3. Custom Blocks
Develop custom blocks for unique brand sections or complex layouts.
4. Staging & Review
Staging mirrors production, editor UX testing, responsive testing, popular plugin compatibility.
5. Documentation & Handoff
Documentation for editors: available blocks, how to use, pre-built patterns, limitations.
FAQ
Can I use Elementor alongside Gutenberg?
Yes, but not on the same pages. Gutenberg for design system, Elementor for custom pages if needed. Or just Gutenberg (cleaner).
If I switch from Kadence to FSE, what happens?
Your content stays. Custom blocks stay. May need minor visual tweaks if Kadence had unique widgets, but core remains stable.
Will my editors find blocks easy to use?
Yes, if documented well and patterns pre-built. Gutenberg is intuitive for WordPress users.
When use custom blocks vs core Gutenberg blocks?
Core blocks handle ~90% (paragraph, heading, gallery, embed, etc). Custom blocks for brand-specific logic or data-driven output.