Website and content architecture
Define the page types, the content model and the navigation logic before layout — so the site can carry material it does not have yet.
Services
Website Development
Build a better digital home: a website structured around content, search visibility, performance and accessibility, so it can keep evolving instead of being rebuilt again.
The problem
Most websites are replaced because of structure, not because of design.
A website usually stops working long before it looks dated. The content model cannot express new material, every page becomes a bespoke layout, performance drifts as third-party scripts accumulate, and accessibility is treated as an audit rather than a build requirement.
At that point a redesign only repaints the surface. Eighteen months later the same limits return, and the business pays for a third rebuild instead of an evolution.
Who it is for
- Businesses whose website cannot express new content
- Teams stuck editing bespoke one-off pages
- Organisations with performance or accessibility exposure
- Companies weighing a rebuild against another redesign
What JMG Group does
The actual work involved.
CMS architecture
Choose and structure the content system around how the team actually publishes: structured fields, reusable blocks, sane editorial roles and portable content.
Rebuild versus redesign assessment
Separate the presentation problems from the structural ones, so budget goes where the limitation actually lives.
Performance and Core Web Vitals
Rendering strategy, image and font policy, script budget and measurement on real devices — LCP, INP and CLS treated as build constraints.
Accessibility as architecture
Semantics, landmarks, focus order, contrast and keyboard paths built into the component library rather than remediated afterwards.
Scalable templates and components
A small set of composable templates and components, so the tenth change costs about the same as the first.
Core capabilities
What is included.
- Website architecture
- Content modelling
- CMS architecture
- Rebuild vs redesign assessment
- Server-rendered delivery
- Core Web Vitals performance
- WCAG-aligned accessibility
- Template and component systems
- Search-friendly technical foundations
- Long-term maintainability
How it fits the wider system
Never delivered in isolation.
A website is the surface every other capability arrives through. It has to be structured so search, content, measurement and later product work can attach without another rebuild.
- Search
- URL structure, rendering and internal linking are decided in the build, not bolted on.
- Content
- Structured content lets one record appear correctly across templates and feeds.
- Growth
- Landing pages and conversion paths reuse the same components instead of forking the site.
- Application
- When a page grows accounts and state, it moves into the application layer deliberately.
- Measurement
- Analytics and performance budgets are set against defined pages before launch.
Typical engagement
How the work runs.
- 01
Assess
Audit the current site: structure, content model, performance, accessibility and the real editing workflow.
- 02
Model
Define page types, content structure, navigation and the template set.
- 03
Build
Implement components and templates against performance and accessibility budgets.
- 04
Migrate
Move content and URLs with redirects planned before launch, not after.
- 05
Evolve
Extend the template set as the business changes, instead of restarting.
Related work
Where this thinking shows up.
Website Development insights
- InsightWhen should a website become a web application?Where the line between a content website and an application actually sits.
- InsightWebsite rebuild vs redesign: how to decidePresentation problems versus architectural ones, and which budget each deserves.
- InsightCMS architecture: choosing the right content systemContent operations, structured content and keeping the material portable.
- InsightWebsite performance and Core Web VitalsLCP, INP, CLS and what performance looks like on real devices.
- InsightAccessibility as website architectureSemantics, components and what automated testing can and cannot catch.
- InsightBuilding a website that can evolveModular architecture and the cost of the tenth change.
- InsightSEO as architectureWhy search visibility is decided by structure long before content is written.
Related services
Capabilities that usually travel with this one.
SEO & Content Architecture
Search visibility designed into the structure of the platform: crawlable routes, coherent hierarchy, topical depth and content systems that scale.
View serviceApplication & PWA Development
Installable, fast, accessible applications built as business systems — with authentication, data, dashboards and structure that hold up after launch.
View serviceDigital Growth Strategy
Treating acquisition, conversion and retention as one connected system, measured against defined outcomes rather than channel-level vanity metrics.
View serviceDiscuss your website.
Bring the current site, the content you publish and where it stops working. We will separate the presentation problems from the structural ones before quoting a build.