BUILD / SHAPE / CONNECT
WordPress
Plan a WordPress website around the content people need.
A WordPress brief starts with the information a website must hold and the people who will keep it current. Page structure, editing choices and integrations should support that work. A clear content model is more useful than a long list of plugins without defined responsibilities.
ORIGINAL EXPLANATORY CONCEPT / NO CLIENT RESULTS
CONTENT / EXPERIENCE
Context
Context
Experience
Ownership
WordPress — the relationships to plan.
01 / THE IMPORTANT CONNECTIONS
Start with the decisions that shape the experience.
Use context, experience and ownership as a starting point for a focused discussion.
01
Context
Start with the pages, people and systems involved. Identify the primary visitor task before choosing features.
02
Experience
Review the content hierarchy, interaction states and responsive layout together. Resolve unclear journeys before development.
03
Ownership
Choose a WordPress content model around what editors repeatedly change. Test headings, images, links and reusable sections in the block editor, then document the difference between editing a page and changing a shared template.
THE APPROACH / FOUR USEFUL STAGES
A process built around a useful decision.
01
Define the customer task
Start with the pages, people and systems involved. Identify the primary visitor task before choosing features.
02
Shape the content and interface
Review the content hierarchy, interaction states and responsive layout together. Resolve unclear journeys before development.
03
Build and connect the platform
Implement the agreed content model and connections in the selected platform. Keep ownership and third-party costs visible.
04
Test, document and hand over
Check real tasks on representative devices. Document editing, access, backups and the responsibilities after launch.
A LITTLE CLARITY BEFORE THE NEXT STEP
Questions worth asking.
What should I bring to a wordpress discussion?
A WordPress brief starts with the information a website must hold and the people who will keep it current. Page structure, editing choices and integrations should support that work. A clear content model is more useful than a long list of plugins without defined responsibilities. Bring the existing website or a representative example, explain the customer task and identify the constraints or decisions that are still open.
How do we review context?
Use a representative scenario and agree what a useful outcome would look like before changing the wider experience. For WordPress, the discussion should connect context with experience and the people who will maintain the result.
What happens after the initial discussion?
The next step is to agree whether a scoped review or project is appropriate. Deliverables, access, dependencies, costs and timing need to be confirmed for that engagement. A conceptual illustration on this page does not represent a completed client project or promise a result.
YOUR NEXT CHAPTER
Make the next decision about wordpress a clearer one.
Tell us what you want to improve, the content and systems involved, and what a useful next step would look like. We can use that context to discuss a suitable scope.