Directus CMS: content records, access and delivery
Evaluate Directus for retail content records. Check schema, editor access, API delivery and hosting, while keeping private and transactional data separate.
- Published
- Last updated
Directus CMS gives editors a structured interface to database content and lets a website retrieve that content through an application programming interface (API). For retail publishing, define the guide and policy records it owns, then restrict delivery to approved public content. Connecting a database alone doesn’t connect the store’s commerce operations.
Decide which records Directus owns
Directus collections are database tables with additional settings for editing and delivery. You can use them for buying guides and store policies while keeping the commerce platform responsible for stock and transactions.
For a hypothetical outdoor retailer, Directus could own tent-selection advice and care guides. Each guide could reference catalogue product identifiers. The catalogue would continue to own the product’s price and availability. A guide’s product reference must resolve through a deliberate integration before the storefront can display current product details.
Write down each record’s owner before designing collections. Keep payment details and customer records outside the public editorial model. If Directus also administers private business data, give it separate collections and explicit permissions. A guide author’s ability to edit advice must not confer access to customer information.
Model content for the editors
Build the editorial model around the records people maintain. A guide needs a stable identifier, body content and its product references. Media needs a usable description and a relationship to the guide that displays it.
Directus supports relationships between collections, including many-to-many relationships through a junction collection. Use that when several guides reference several catalogue entries. If the catalogue stays outside Directus, store its stable identifier and define how the integration detects a deleted product.
Give editors labels that describe their task and validation that catches incomplete records. For example, require a guide title and prevent an empty catalogue identifier in a product reference. Separate the right to change text from the right to change publication state.
Review an editor’s effective access across all assigned policies. Directus combines policy grants additively, so a restrictive policy cannot cancel access another policy grants. Use a non-administrator account to assess the resulting editing form.
Media has its own access boundary. The file access documentation explains that file permissions apply through the API. Permit the public images a guide needs without exposing internal attachments or exported records.
Publish the intended public records
Directus delivery must enforce record and field permissions before the frontend renders the response. Its access-control documentation states that public permissions start disabled. Granting unrestricted collection read access can expose unpublished items too.
Use a read policy that permits only published guides and an explicit set of public fields. Keep editorial notes unavailable to that identity. A frontend filter makes a request narrower, but the access policy must enforce the boundary when someone changes that request.
Here is a hypothetical response contract for a guide. The stored record contains an internal supplier note. The public response contains only the guide fields:
{
"data": [{
"id": "tent-care",
"title": "Caring for your tent",
"body": "Dry the tent before storing it.",
"catalogue_ids": ["TENT-42"]
}]
}
Assess that contract against your chosen Directus version in an isolated test project:
- Create one published guide and one unpublished guide with different text. Add an internal note containing dummy data to both.
- Request the collection using the public delivery identity. Use the query parameters to select the intended public fields. Confirm that only the published guide appears.
- Request the internal field explicitly and try a broader field selection. Neither response must contain the dummy note. Inspect expanded relationships and file access under the same identity.
- Save a changed draft through the editor account. Confirm that public delivery retains the approved text while an authorised preview retrieves the draft.
- Publish the revision and run the frontend’s refresh path. Confirm that the public page displays the new text and any separate answer-source import uses it too.
Content versioning is enabled per collection. The documented workflow saves changes in a version before publication. Editors need the documented permissions for versions and revisions as well as the content collection. Publishing a version updates the published item, but the website’s build or cache refresh remains a separate responsibility.
If a published revision appears in the API but the page stays old, inspect the frontend refresh trigger and cache. If a draft appears publicly, fix the delivery policy before examining page styling.
Choose and maintain the deployment
Directus has managed cloud and self-hosted options. Its hosting overview describes Directus Cloud as maintained by the Directus team. Self-hosting gives your team responsibility for the infrastructure, including the database and backups.
For a managed deployment, settle the service’s resource limits and backup recovery arrangements alongside the editorial requirements. For self-hosting, assign responsibility for monitoring and storage, then rehearse restoring the database and media together.
Licensing also depends on the version and deployment you choose. The current licensing documentation names the Monospace Sustainable Core License. Unlicensed self-hosted instances run on a core tier, with additional capabilities or higher limits requiring a licence. It also documents an Open Innovation Grant with eligibility conditions. Include Studio seats and related collections in the assessment rather than relying on historical licensing summaries.
Before an upgrade, read the breaking-change guidance and rehearse it against a restored test copy. Repeat the public-response checks after changes to permissions or versions.
For portability, Directus can export collection items in several formats, including JSON and CSV. An item export alone isn’t a full recovery plan. Preserve the schema and access configuration alongside media and deployment settings. Keep exports containing private fields in a location public file permissions cannot read.
Choose Directus when your team needs structured editorial records and can maintain the delivery boundary. Complete the assessment when an editor can publish a guide, the public response excludes private data and a restored copy reproduces both behaviours.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.