Deliver home, services or products, about, contact and agreed supporting pages. Organise around understanding and enquiries and adapt the design to real material.
Working material
Implementation includes normal, empty, error and recovery states. The interface provides feedback while the server owns authorisation, validation and persistence.
Delivery and checks
Test valid, invalid and missing inputs, including back, retry and duplicate handling. Keep release records and usable recovery material.
Related practical notes
Help customers understand the business, explore its offering and start a conversation through clear information and brand presentation.
Service copy
Project discipline
Define service copy responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Attributing technical work clearly
Distinguish authors, reviewers and implementers and confirm names and titles. Let technical explanation carry the article rather than relying on awards.
Practical notes
Why it’s time for the Jamstack to shine – the technology perspective
Test builds, releases, caching and dynamic requests separately. Architecture labels cannot guarantee unlimited free capacity.
Practical notes
Showing evidence of technical delivery capability
Show verifiable scope, testing records and maintenance practices. Publish partner levels or audit conclusions only with supporting evidence.
Accessibility checks
Project discipline
Define accessibility checks responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Upgrading v rebuilding your Kentico website
List retained assets, rebuilt content, interface changes and tests. A clear problem inventory helps identify what should remain.
Specification comparison
Project discipline
Define specification comparison responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Stop trying to be all things to all people
Answer a primary audience’s core question first and give secondary services distinct routes. The homepage should guide rather than contain everything.
Brand positioning
Project discipline
Define brand positioning responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Benefits of the Jamstack – from buzzword to business ready
Static delivery suits content that can be prepared ahead of time. Live pricing, stock and authentication need separate data paths; draw that boundary before choosing an architecture.
Practical notes
Presenting a developer’s contribution
Show maintained components, technical explanations and verifiable contribution links. Do not add certifications or awards that have not been supplied and verified.
Practical notes
GILT or GUILT – Localisation crimes
Separate language, dates, currency, reading direction and form rules. Review translated pages with real data for length changes and local meaning.
Component maintenance
Project discipline
Define component maintenance responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Form validation
Project discipline
Define form validation responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Account permissions
Project discipline
Define account permissions responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Keeping recognition information accurate
Record provenance and publication dates and review current terminology. Rebranding a page must not transfer another organisation’s facts.
Practical notes
Showing content-platform implementation capability
Explain modelling, migration and editorial training with inspectable examples. Exclude unconfirmed partnership status from public descriptions.
Related practical notes
Help customers understand the business, explore its offering and start a conversation through clear information and brand presentation.
Practical notes
How to choose the right CMS
Use an article, product and approval as sample tasks. Have real editors author, preview and restore content and record assistance and maintenance costs.
Practical notes
Building a martech stack
Map acquisition, content, email, analytics and customer records, including existing tools. Before adding a system, check export, synchronisation and maintenance ownership.
Practical notes
Plan human review for AI content
Generating a whole website and then looking for someone to check it encourages a rushed review. Decide beforehand which material is available, which statements need approval and who can publish the result. The draft can then be built around information that is possible to verify.
Practical notes
How to create a digital strategy roadmap
Separate current problems, near-term improvements and later experiments, with owners and evidence. Keep the rationale for roadmap changes traceable.
Practical notes
How to perform a website audit
Sample navigation, copy, images, forms, search and mobile tasks. A successful response establishes reachability, not correct content or behaviour.
Practical notes
How to brief a digital agency
State the business, audience, pages, available material and decision-maker. Clarify budget and timing conditions and identify specific reference sections.
Planning headless CMS content
Download this editable planning headless cms content to record current work, open questions and owners. OXOAK examples can be adapted to the project.
Digital product design workbook
Download this editable digital product design workbook to record current work, open questions and owners. OXOAK examples can be adapted to the project.
Practical notes
Why conducting a content audit is essential
Record URL, topic, owner, validity and action. Distinguish duplicates, outdated material and unsupported claims rather than deciding from traffic alone.