This site doesn't use WordPress. It's built with a static site generator - currently Jigsaw, previously Gatsby. I didn't land here by accident; I chose this approach because it fits what this site needs. Here's why, and when WordPress is still the right call.
Why I Don't Use WordPress for This Site
This site is a portfolio and small blog. It doesn't need a CMS, a database, or dozens of plugins. I could absolutely use WordPress - I've worked with it for over 15 years and I do WordPress development for clients regularly. But for this site, it would be overkill. A static site generator gives me what I actually need:
- Speed: Every page is plain HTML. No database queries, no PHP on each request, no plugin overhead. There's nothing to slow the site down - it just loads.
- Simplicity: No database to back up, patch, or secure. No admin panel to harden. Content lives in files; I edit, build, and deploy.
- Cheap, easy hosting: Static files can run anywhere - GitHub Pages, Netlify, a basic server. No need for managed WordPress or a beefy PHP stack.
- Security: No admin panel, no login page, no database, no plugins to patch. There's no attack surface on the live site - nothing to hack. Contrast that with WordPress, where security is an ongoing concern (something I help WordPress clients with regularly).
- Fit for the job: A portfolio and a small blog don't need a CMS. Occasional posts and page tweaks are fine with a rebuild. For this use case, a static site generator is the right tool.
This workflow suits me because I'm a developer. I'm comfortable editing files in a code editor, running builds, and deploying from Git. Posts are published automatically via GitHub Actions - I push to a branch with a future date, and it goes live on schedule without me touching it. That's a great workflow for a developer. For a non-technical person who needs to update content regularly, WordPress (or a similar CMS) is almost certainly a better fit.
The trade-offs are real: no CMS (I edit content in files), no dynamic features (e.g. search or comments without third-party services), and you rebuild to update. For a site like this, those trade-offs are acceptable. For a content-heavy site with non-technical editors, they usually aren't - and that's when WordPress or something else makes sense.
Static Site Generators: Gatsby, Then Jigsaw
A static site generator takes templates and content and builds them into plain HTML at build time. There's no server-side processing when someone visits - just pre-built pages served directly. There are dozens of generators to choose from; I've used two.
Gatsby - I used Gatsby for this site for several years. It's React-based, has a huge ecosystem, and offers a great developer experience. It's a solid choice for many projects. But for a simple portfolio and blog, it was heavier than needed: a full React framework, client-side hydration, service worker caching that made updates fiddly, and more tooling than the job required.
Jigsaw - I switched partly to try something different and partly because Jigsaw suited this site better. It's PHP and Blade (familiar from my Laravel work), with a simpler toolchain. The main draw: a flatter HTML/page structure. No client-side JavaScript framework, no hydration - just plain HTML pages. That's better for search engines and AI crawlers that want clean, simple markup.
The switch wasn't because Gatsby was bad - it was about fit. Same reason this site isn't WordPress: choose the tool that matches the job.
Right Tool for the Job
I don't recommend the same solution to every client or every problem. No one size fits all. The right choice depends on what you're building, who updates it, and what you need it to do.
When WordPress makes sense: Content-heavy sites, non-technical editors who need a CMS, blogs or marketing sites that rely on plugins (forms, SEO, e-commerce). WordPress is familiar, well-supported, and often the right fit. I do WordPress development for clients in Bath, Bristol, and Wiltshire when it's the right tool - and I've written about WordPress performance when you want to make an existing site faster.
When static (e.g. Gatsby, Jigsaw) makes sense: Marketing sites, portfolios, docs, landing pages - where content changes occasionally and speed and simplicity matter. No database, no CMS, minimal hosting. This site is one example.
When Laravel (or a framework) makes sense: Applications, dashboards, APIs, user-generated content, complex business logic. You need a proper backend. For that I recommend Laravel for most new projects (and Symfony when it's the right fit). I've written about when to hire a Laravel developer in Bath & Bristol and when to hire a freelance backend developer - both are about choosing the right kind of help for the problem.
Common Questions
When should a site be WordPress?
When you need a CMS for non-technical editors, content-heavy sites, or plugin-based features like forms, SEO tools, and e-commerce. WordPress is familiar, well-supported, and often the right fit for marketing sites and blogs where multiple people update content regularly.
When does a static site make sense?
For portfolios, marketing sites, documentation, and landing pages where content changes occasionally and speed and simplicity matter. No database, no CMS, minimal hosting costs. If you're the only one editing and updates are infrequent, static can be ideal.
When do you need Laravel or a framework?
For applications, dashboards, APIs, user-generated content, or complex business logic that needs a proper backend. If users log in, interact with data, or you're building something beyond a brochure site, you need a framework - Laravel for most new projects, Symfony when it's the right fit.
What's the difference between Gatsby and Jigsaw?
Gatsby is React-based - great for interactive sites and projects that benefit from the React ecosystem. Jigsaw is PHP/Blade - simpler and lighter for straightforward static sites, especially if you already work with Laravel. Both compile to HTML at build time; the difference is in tooling, complexity, and what you're comfortable with.
Choosing the Right Stack
Choosing the right stack matters. A static site for a portfolio; WordPress for a content-heavy site with editors; Laravel for an app. I help clients in Bath, Bristol, Wiltshire, and across the UK appraise the options - whether you're starting from scratch, outgrowing WordPress, or wondering if a simpler stack would serve you better.
If you're not sure whether your site should be WordPress, static, or something else, get in touch. I can help you decide.