Home Ideas and insights

Showing solution capability in a portfolio

OXOAK / Content and design

Practical notes

1 min read

Showing solution capability in a portfolio

Show goals, constraints, decisions and validation, stating connected systems. A clickable mockup is not an operating business system.

Putting content management into practice

A content model defines independently maintained and reusable information. Authoring, preview, approval and publication form a workflow; an API response validates only one part.

Checking the result

Have real editors create, change and restore content using long headings, missing fields and multiple languages. Record development dependencies and release ownership.

Related design commentary

Practical notes

Assessing a CMS release for marketing work

Have editors test authoring, campaign preview and approval. Include training and migration rather than updating technical packages alone.

OXOAK / Editorial

Practical notes

Yuechang Sports · AI-generated concept illustration

Yuechang Sports | Brand & content

Concept case · Connecting events, venues and sports culture through a clear visitor journey.

Practical notes

Optimizely's Opal AI: A bright spark or just more AI hype?

Test generation, revision and publication with your own material. Revalidate demonstration steps under project constraints, including failures and permissions.

OXOAK / Editorial

Practical notes

Vocus · Design showcase

Organise communications around individual and business needs, with clear routes to capability, products and support.

The Fred Hollows Foundation · Design showcase

Connect people, projects and action in a non-profit narrative, with discoverable use-of-funds and progress information.

Practical notes

Designing task-based AI training

Cover input preparation, output review and permission boundaries. Require an independent task and an explanation of when to stop using the tool.

OXOAK / Editorial

Practical notes

Eftsure · Design showcase

Connect a software product's problem, capabilities and workflow, separating demo requests from resources.

Allens 200 · Design showcase

Use a chronology to connect people, events and images, with clear cues for browsing by period.

William Angliss Institute · Design showcase

Organise vocational education by field, level and application requirements, using learning environments to add context.

Legalsuper · Design showcase

Separate plan information, resources and account actions on a member site, explaining complex concepts in short passages.

Fuso · Design showcase

Support vehicle comparison through models, applications and specifications, pairing imagery with technical information.

RedZed · Design showcase

Explain specialist financial services through customer situations and process, with conditions before enquiries.

Practical notes

Designing venue information for search-led visits

Make event times, transport, ticket conditions and FAQs self-contained. Search visitors need current information and an authoritative confirmation route.

OXOAK / Editorial

Practical notes

Validating specialist AI implementation capability

Use a real brief to demonstrate data retrieval, human approval and failure recovery without exposing unauthorised customer information.

OXOAK / Editorial

Practical notes

Comparing AI agents for marketing tasks

Use the same campaign brief to compare research, drafting and release preparation. Record provenance, editability and authorisation requirements alongside speed.

OXOAK / Editorial

Practical notes

Why you should upgrade to Optimizely CMS 12

Inventory extensions, APIs and deployment constraints and regress representative content and roles. Confirm current documentation rather than treating historical guidance as current advice.

Practical notes

Verifying annual partner achievements

Compile scope, releases and permissions and evidence recognition separately. Use methods rather than achievement announcements when records are unavailable.

OXOAK / Editorial

Practical notes

Separating credentials from delivery responsibility

Confirm the contracting party, implementation scope and maintenance owners before checking credentials. State additional purchases even where external certification exists.

OXOAK / Editorial

Practical notes

Optimizely multi-site best practices: a presentation by MVP Ynze Nunnink

Separate global fields, site overrides and permissions and test change propagation. Check all referencing sites before removing shared content.

Practical notes

Using industry evaluations in platform selection

Check evaluation scope, criteria and period, then validate real tasks. Ranking does not replace budget, implementation and editorial assessment.

Practical notes

Showing solution capability in a portfolio

Show goals, constraints, decisions and validation, stating connected systems. A clickable mockup is not an operating business system.

OXOAK / Editorial

Practical notes

Veggycation · Design showcase

Categorise educational food content by ingredient, question and use case, using visual indexes for discovery.

Life-Space Probiotics · Design showcase

Explain product ranges and audiences first, distinguishing brand storytelling from product information.

Practical notes

A multi-brand strategy in Optimizely DXP

List shared components, brand-specific assets and publishing permissions. Check that brand switching does not accidentally transfer another brand’s cart, form draft or tracking identity.

Practical notes

Keep reading

A multi-brand strategy in Optimizely DXP

List shared components, brand-specific assets and publishing permissions. Check that brand switching does not accidentally transfer another brand’s cart, form draft or tracking identity.

OXOAK / Editorial

Practical notes

A tutorial on building a .NET Core website with Umbraco Headless

Isolate content retrieval and separate preview credentials from public read access. Define fallbacks for missing fields so an editorial update cannot unexpectedly break an entire page.

OXOAK / Editorial

Practical notes