The Problem: The Weight of WordPress
The original iteration of theHomeoffice.ie was built on WordPress, acting as a directory for remote working hubs across Ireland. Initially, it served its purpose, but as the dataset grew to encompass 365 hubs across 26 counties, the architectural cracks began to show.
WordPress is fundamentally a blogging platform. Forcing it into a relational data structure — managing complex relationships between counties, amenities, pricing tiers, and hub locations — requires a precarious stack of plugins (Custom Post Types, Advanced Custom Fields, caching layers). This resulted in sluggish query times, a fragile maintenance loop, and a hosting bill that didn’t align with the revenue model of a nascent directory. The “shape” of the data was dictated by the CMS, rather than the needs of the product.
The Decision: Selecting the Right Stack
I needed a system that treated data as data, not as a collection of web pages. The evaluation process was straightforward:
-
WordPress (Status Quo) Too slow for a massive directory, required expensive hosting to handle complex database queries, and offered a poor developer experience for structured data.
-
Next.js Excellent for dynamic applications, but overkill for a directory where the data changes infrequently (perhaps weekly). The client-side JavaScript payload was unnecessary overhead for a content site focused on SEO.
-
Astro + Storyblok The winning combination. Astro provided zero-JS static site generation for lightning-fast page loads. Storyblok offered a robust, visually editable headless CMS that treated data structurally, allowing for infinite scaling without performance degradation.
What Got Built: A Scalable Static Architecture
The new architecture fundamentally separated the content repository from the presentation layer.
Storyblok as the data engine. We defined strict block schemas for ‘Hubs’, ‘Counties’, and ‘Regions’. This structured approach meant a hub’s data wasn’t just HTML mixed with text; it was a pure JSON object detailing amenities, coordinates, and contact info. This semantic structure makes the data highly readable not just to human users, but to AI crawlers and large language models, future-proofing the directory for AI-driven search experiences.
Astro as the build engine. At build time, Astro queries the Storyblok API, pulls down the entire structured dataset, and generates hundreds of static HTML pages. It handles the complex routing logic (e.g. /hubs/munster/cork/the-republic-of-work) seamlessly. The result is a site that requires no database connection at runtime.
Outcomes: Performance and Efficiency
The transition yielded immediate, measurable improvements across all core metrics:
Conclusion: What This Was Really About
Ultimately, this project wasn’t just about escaping WordPress; it was about adopting a philosophy of structured data over unstructured documents.
By moving to a headless architecture, theHomeoffice.ie transformed from a slow, monolithic website into an agile, highly performant dataset with a web presentation layer. It scales effortlessly, costs pennies to host, and is structurally prepared for whatever the next generation of search and discovery demands.
