Michael Edwards

← Posts

Architecture Decisions That Aged Well (and Didn’t)

Placeholder image for Michael Edwards' portfolio

Publication Date: 15 May 2026
Author: Michael Edwards

Executive Summary

Architectural decisions in web development carry long half-lives. A framework choice or abstraction layer introduced today will shape developer productivity and platform stability for years to come.

This post evaluates monoliths, headless REST API setups, and shared design systems across multi-brand enterprise platforms.

Evaluating the Patterns

1. Shared Gutenberg Block Design Systems (Aged Extremely Well)

Building a central, reusable library of Gutenberg blocks with standardized React components across brand portfolios (e.g., hospitality brands or publishing networks) delivered massive returns in maintainability, accessibility, and brand consistency.

2. Headless WordPress + Next.js APIs (Aged Well for Specific Use Cases)

Using WordPress as a headless CMS powered by REST APIs and Next.js frontends proved highly effective for global brand sites requiring bespoke frontend interactions and tight API integrations.

3. Over-Engineered Third-Party Plugin Dependencies (Aged Poorly)

Relying on heavy monolithic third-party plugins for core features like internationalisation or custom layout building introduced severe technical debt, security vulnerabilities, and upgrade friction over time.

Conclusion

Invest in clean API boundaries, modular component libraries, and custom light-footprint PHP layers for core business logic.