← Back to the Knowledgebase

Website Frameworks Explained: Choosing How Your Site Gets Built

"Should we do it in WordPress?" is really a question about machinery. Every website is assembled from HTML, styles, some JavaScript and, usually, a system that stores the content. What people call a framework is a decision about how much of that machinery you take on — and that decision sets your running costs, your page speed and how much upkeep you have signed up for. Here are the options in plain English, with a table to decide from.

What People Mean by a Framework

A website framework is the foundation your pages are assembled on: the tools and conventions that decide how a page is created, where its content lives, and who is able to change it. It is less about fashion than about upkeep. Some choices hand you a dashboard and a list of things to update; others hand you finished files and nothing to maintain.

Three questions settle most decisions. How often does the content change? How large is the catalogue of products or services? And who looks after the site once it is live — you, an in-house developer, or an agency? Answer those honestly and the right option usually narrows itself down.

Same website, very different bills: the difference between two options is rarely how they look on day one. It is how much work, cost and risk accumulates over the following years, and how quickly the site still loads while all of that accumulates.

The Main Options, With Their Trade-offs

Five routes cover almost every business website. Each one is a good answer to a different question.

Static HTML — the pages themselves

Static HTML is the baseline everything else is measured against. The browser receives finished pages of markup and styles: there is no content engine running behind them, no admin login to protect and no software stack that needs patching when a security advisory lands. That is why it is the fastest option and the cheapest to run — there is simply less between the visitor and the page. Sites like this are also pleasantly boring to host, which keeps the monthly cost down.

Best for / Watch out for

Best for: brochure sites, portfolios, campaign pages and anything that changes rarely; businesses that want the smallest possible maintenance bill.

Watch out for: every new page or rewrite is a file edit, so a site with hundreds of articles becomes unwieldy; you need someone comfortable editing the files, or an agency that does it for you.

WordPress — the content system

WordPress is a content system rather than a set of pages: content is stored in a database, a theme supplies the design, plugins add features, and editors publish through a dashboard. That is exactly why it suits content-heavy sites — a blog, a news outlet, a firm publishing case studies every month — where several people need to add and edit material without touching code.

The dashboard is also what needs looking after. WordPress, your theme and your plugins are all software, and software needs patching when updates are released. A site that is never updated accumulates risk, and a site with a long plugin list has more moving parts to keep compatible with each other.

Best for / Watch out for

Best for: content-heavy sites, publishing teams, and businesses that want non-developers to keep the site current.

Watch out for: regular core, theme and plugin updates, plugins that can conflict with each other, and a host that has to run the whole stack comfortably.

Magento / Adobe Commerce — the large catalogue

Magento, now sold as Adobe Commerce, is built for catalogues at scale: deep product ranges, layered navigation, intricate stock and pricing rules, multiple store views and teams of merchandisers working on the shop at once. It brings real machinery with it — a heavier hosting footprint, a build and deployment process, and developers who specialise in the platform.

For a small shop, that machinery is cost without the benefit. For a large or complex catalogue it is the point: the complexity lives in the catalogue anyway, and this is the platform designed to hold it.

Best for / Watch out for

Best for: large or complex catalogues, multi-brand or multi-region trading, and businesses with developer support behind them.

Watch out for: the heaviest option here — more demanding hosting, longer builds, and specialist skills that are not cheap to hire or train for.

The commerce angle — Shopify and WooCommerce

If you are selling, there is a second decision underneath: how much of the shop you rent and how much you own. Shopify is a hosted platform — storefront, checkout, hosting, security and payments are the platform's job, on a recurring subscription. You are trading quickly and renting the machinery. WooCommerce is WordPress with a shop attached: it runs on your own hosting, keeps everything inside the WordPress dashboard you may already use, and leaves updates and extensions in your hands.

Best for / Watch out for

Best for: Shopify — getting to market fast without running a commerce stack; WooCommerce — an existing WordPress site that wants a shop in the same admin area.

Watch out for: a platform plan is a permanent running cost with platform-specific limits; WooCommerce hands the maintenance, the extensions and the hosting decisions back to you.

Modern JavaScript frameworks — React, Next.js and Astro

React, Next.js and Astro change how pages are assembled rather than what a page is. The interface is built from reusable components; pages can be rendered on the server, pre-built before a visitor arrives, or both. The payoff is richer interaction and carefully controlled performance, which matters when the site behaves like an application: a dashboard, a configurator, a booking tool with live availability.

When the site is a brochure with a contact form, those frameworks are mostly a build step, a toolchain and another dependency for a developer to maintain — without making the page meaningfully faster than a plain, well-written static page. Adopt them when the interaction is the product, not because they are modern.

Best for / Watch out for

Best for: web apps, dashboards, configurators and search-heavy experiences; teams that already work in JavaScript.

Watch out for: build tooling and developer time you pay for on every future change; simple marketing pages rarely need any of it.

The Decision Table

The same five options, lined up on the four things that actually decide the choice. Costs and complexity are relative to each other rather than quoted, because they move with your host, your scope and who does the work.

Website framework choices compared: running cost, speed, complexity and best fit
Option Running cost Speed Complexity Best fit
Static HTML Lowest — hosting only Fastest; nothing to run per request Simple to host; content edits are file edits Brochure sites, portfolios, pages that rarely change
WordPress Low to moderate; hosting plus upkeep Moderate; depends on theme, plugins and host Moderate; publishing is easy, patching is ongoing Blogs, news, content-heavy business sites
Magento / Adobe Commerce Higher; specialist hosting and support Heaviest; more machinery behind each page High; needs specialist developers Large catalogues, complex stock and pricing
Shopify Recurring platform subscription Consistent; managed by the platform Low to moderate; hosted, so no stack to run Shops that want to trade quickly and rent the machinery
WooCommerce Hosting plus the extensions you add Moderate; follows your WordPress setup Moderate; you own the updates Existing WordPress sites adding a shop
React / Next.js / Astro Moderate; hosting plus developer time Fast when rendered or pre-built with care High; build tooling and JavaScript skills Web apps, dashboards and interaction-heavy tools

And the Agent Frameworks

The word "framework" turns up somewhere else entirely. On fullauto.online we keep a leaderboard of the agent frameworks — LangGraph, CrewAI and their neighbours — which are the toolkits used to build software that plans and acts on your behalf.

A website framework decides how pages are assembled and served to the people reading them; an agent framework decides how a piece of software breaks a goal into steps, calls tools and coordinates the work until the goal is done. One produces pages, the other produces actions — they share a word, not a job.

Also from Daedalus Design: see how AI is changing the business behind the website, and our leaderboards for the tools we track.

How We Build

We work in three ways, and the framework conversation is the first thing we have with a new client. Our AI-managed websites pair a fast, lightly engineered site with assistants that keep it fed with content and answers. Our standard web design service is the hand-built, no-plugin route for businesses that want something lean and predictable, and our web design overview explains how the two compare and when WordPress or Magento is genuinely the right call.

If you are not sure which route fits, tell us how the site will be used and we will tell you what we would build — including when the honest answer is the simplest one.

Last updated: 8 November 2026

Not Sure Which Option Fits Your Business?

Compare what each route costs and what is included, or talk it through with us and get a straight recommendation.

See Packages → Talk to Us →