# OXOAK · Headless CMS guide

Replace examples with project material and assign owners to open questions. Do not include passwords.

## Why consider headless

Separating content models from presentation can support reuse across pages, languages and channels. List actual reuse needs and compare conventional CMS editing for simpler sites.

## Content models and taxonomy

Define fields, relationships and required values for products, services, people and resources. Test long titles, missing images and both languages instead of using a single HTML field for everything.

## Editing, preview and review

Editors need to locate changes on a page and distinguish saving, preview and publication. Have content owners create, revise and review an entry, recording steps that require help.

## API and frontend ownership

A content API supplies data; routing, layouts, search, forms and errors still require implementation. Assign ownership for schema changes, failed requests and limits.

## Languages and permissions

Define shared and translated fields and missing-translation behaviour. Assign editor, reviewer and administrator permissions and test denied actions with separate accounts.

## Search, URLs and migration

Inventory URLs, documents and metadata and record retained, merged and removed content. Check images, links, redirects and readable content in a migration sample.

## Publication and caching

Compare the published URL with its preview and establish cache refresh and retry behaviour. Track content and code releases separately and retain recovery sources.

## Selection and maintenance

Compare editing, frontend maintenance, hosting and required extensions using identical content. Record account ownership, subscriptions, backups and exit costs before choosing.