Deliver journeys, permissions, data rules, states and evidence. Implement accounts, search, files and operations explicitly rather than presenting screenshots as an application.
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. | ||||
| Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach. |
Contact OXOAK · Contact OXOAK · Contact OXOAK · Contact OXOAK · Contact OXOAK · Contact OXOAK
- Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach.
Web applications · Working details
Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach.
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.
Home · Contentful · Storyblok
Related design commentary
Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach.
Diaverum d.CARE app · Design showcase
Clarify user roles and current tasks in a service app, with visible states for records, reminders and help.
Qiju Electric | Considered product choices
Concept case · Connecting living spaces, product discovery and planning to make technical choices clearer.
AusAppPathways App · Design showcase
Support short mobile career exploration sessions with coherent filters, return positions and saved preferences.
Related practical notes
Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach.
Search experience
Project discipline
Define search experience responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
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.
Release recovery
Project discipline
Define release recovery responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
We rebuilt our website on the Jamstack (without changing CMS)
Separate retained models from changed frontend routes and test preview, release and caching. Retaining an API does not automatically preserve old URLs.
Interaction feedback
Project discipline
Define interaction feedback 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.
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
Where is my data anyway? Data sovereignty challenges in a world of SaaS and Cloud
Inventory storage, backups, logs and support access across services and regions. Check contracts and settings rather than primary hosting location alone.
Practical notes
Serving content to IoT devices with a headless CMS
Reuse facts while adapting order and interaction to device tasks. Check length and confirmation separately for small-screen, voice and screenless output.
Visual consistency
Project discipline
Define visual consistency responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.
Practical notes
Building a feedback loop in service partnerships
Keep the problem, resolution and confirmation for support requests. Review recurring issues and turn repetitive fixes into product or content improvements.
Shape the project
Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach.
Related practical notes
Design interfaces for specific tasks and business workflows, confirm the key actions, then choose a suitable implementation approach.
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.
