How to harness AI without being a rocket scientist

How to harness AI without being a rocket scientist

How to harness AI without being a rocket scientist
OXOAK / Content and design

Practical notes

1 min read

How to harness AI without being a rocket scientist

Start with one internal task with clear data boundaries and compare results manually. Define permitted inputs, reviewers and stop conditions before expanding.

How to harness AI without being a rocket scientist

Putting ai workflows into practice

Generated output may omit information or introduce unsupported statements. Separate model output, human approval and execution; a recommendation does not grant release authority.

How to harness AI without being a rocket scientist

Checking the result

Test both sufficient and incomplete inputs and compare accuracy, omissions, rework and stopping behaviour. Verify sources and commitments before public release.

How to harness AI without being a rocket scientist
How to harness AI without being a rocket scientist

Related design commentary

Service copy

Service copy

Project discipline

Define service copy responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

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.

Practical notes

Is a headless CMS good or bad for SEO?

Check rendered content, distinct URLs and metadata. An architecture label does not determine search performance; inspect the delivered page.

Is a headless CMS good or bad for SEO?
OXOAK / Editorial

Practical notes

Practical notes

What is Kentico Kontent? And why should I care?

Practical notes

What is Kentico Kontent? And why should I care?

Model reusable facts, page composition and media separately. Validate authoring and preview before expanding rather than putting everything into one rich-text field.

What is Kentico Kontent? And why should I care?
OXOAK / Editorial

Practical notes

Practical notes

Reviewing a Jamstack implementation

Practical notes

Reviewing a Jamstack implementation

Record build time, release failures, editorial updates and dynamic-endpoint issues separately. Base benefits on project evidence rather than borrowed industry figures.

Reviewing a Jamstack implementation
OXOAK / Editorial

Practical notes

Practical notes

Preparing a headless CMS demonstration

Practical notes

Preparing a headless CMS demonstration

Demonstrate authoring, API delivery and page updates with one model. State applicability and exclude real credentials and private content from examples.

Practical notes

Practical notes

We built our new site using Kentico Cloud (and a few other microservices)

Practical notes

We built our new site using Kentico Cloud (and a few other microservices)

Record each service’s purpose, ownership and failure handling. Test the publication chain and keep accountability clear across providers.

We built our new site using Kentico Cloud (and a few other microservices)
OXOAK / Editorial

Practical notes

Practical notes

Benefits of the Jamstack – from buzzword to business ready

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.

Benefits of the Jamstack – from buzzword to business ready
OXOAK / Editorial

Practical notes

Practical notes

Practical notes

How do you handle online forms with Kontent.ai?

Let the CMS provide page content while a protected endpoint validates and stores submissions. Keep administrative keys out of the frontend and preserve recoverable input.

How do you handle online forms with Kontent.ai?
OXOAK / Editorial

Practical notes

Practical notes

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.

Why it’s time for the Jamstack to shine –
the technology perspective
OXOAK / Editorial

Practical notes

Practical notes

UNICEF Australia · Design showcase

Cross-organise non-profit content by theme, region and participation, retaining sources and updates for important material.

Serving content to IoT devices with a headless CMS

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.

Practical notes

Practical notes

Getting your head around headless content management

Practical notes

Getting your head around headless content management

The content system owns structured material while the frontend owns presentation. Connect preview, release and cache invalidation into one tested workflow.

Getting your head around headless content management
OXOAK / Editorial

Practical notes

Practical notes

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.

Practical notes

Practical notes

Pet Culture · Design showcase

Pet Culture · Design showcase

Organise pet products by animal, life stage and purpose, connecting item information with relevant guidance.

Umbraco Heartcore launch

Practical notes

Umbraco Heartcore launch

Test retrieval, media, previews and publication delay with missing-content states. Managed hosting does not replace frontend and search-content validation.

Practical notes

Practical notes

Legalsuper · Design showcase

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

We rebuilt our website on the Jamstack (without changing CMS)

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.

We rebuilt our website on the Jamstack (without changing CMS)
OXOAK / Editorial

Practical notes

Practical notes

Why you should be modelling content

Practical notes

Why you should be modelling content

Store repeated names, specifications and contact facts as shared fields with page context. Check references after updates to avoid stale values.

Practical notes

Practical notes

Healthylife · Design showcase

Healthylife · Design showcase

Connect product discovery, editorial reading and services, supporting varied shopping stages through search and categories.

Web Spotlight - visual page editing in Kontent (in less than a day)

Practical notes

Web Spotlight - visual page editing in Kontent (in less than a day)

Verify the selected content item, save and inspect the public result. Editable preview and successful publication are separate checks.

Web Spotlight - visual page editing in Kontent (in less than a day)
OXOAK / Editorial

Practical notes

Practical notes

Optimizely as a headless CMS

Practical notes

Optimizely as a headless CMS

Verify retrieval, preview, routing and release triggers with appropriate API boundaries. The frontend still needs independent design and validation.

Practical notes

Practical notes

Umbraco introduces composable DXP offering

Practical notes

Umbraco introduces composable DXP offering

Define interfaces for content, search, analytics and identity and preserve export and replacement paths. Test failure isolation before adding more systems.

Umbraco introduces composable DXP offering
OXOAK / Editorial

Practical notes

Practical notes

What is a composable DXP?

Practical notes

What is a composable DXP?

Map data flows between content, search, analytics and identity with failure owners. Replaceability requires real export and recovery paths.

What is a composable DXP?
OXOAK / Editorial

Practical notes

Practical notes

Jamstack
AI-powered content recommendations with a headless CMS

Practical notes

AI-powered content recommendations with a headless CMS

Define taxonomy, visibility and exclusion rules before connecting recommendations. Similarity must not expose expired, paid or unpublished content.

AI-powered content recommendations with a headless CMS
OXOAK / Editorial

Practical notes

Practical notes

Choosing between Kentico Xperience and Kontent.ai

Practical notes

Choosing between Kentico Xperience and Kontent.ai

Compare authoring, preview, approval and release with the same update. Include frontend implementation and integration ownership in the evaluation.

Choosing between Kentico Xperience and Kontent.ai
OXOAK / Editorial

Practical notes

Practical notes

Practical notes

Configuring Web Spotlight in Kontent for any scenario

Connect preview locations to the correct content items and separate preview from publishing permissions. Recheck mappings after layout changes.

Configuring Web Spotlight in Kontent for any scenario
OXOAK / Editorial

Practical notes

Practical notes