---
title: "Content models"
description: "Decide which content belongs in Shopify and which presentation belongs in Nyxel."
canonical_url: "https://nyxel.dev/docs/content-models"
markdown_url: "https://nyxel.dev/docs/content-models.md"
---

# Content models
URL: /docs/content-models
LLM index: /llms.txt
Description: Decide which content belongs in Shopify and which presentation belongs in Nyxel.

# Content models

Nyxel uses Shopify as the durable source for commerce and structured store content. It does not introduce a second database for products, collections, pages, metafields, or metaobjects.

## Choose the owner by meaning

Content belongs in Shopify when it describes the business or a commerce resource independently of one page layout. Product specifications, collection descriptions, store locations, size guides, FAQ entries, and reusable editorial records are examples.

Nyxel owns how that content appears: which section renders it, where that section sits, which layout variant is selected, which color scheme applies, and which source path supplies a setting.

| Question                                                        | Owner                        |
| --------------------------------------------------------------- | ---------------------------- |
| What is the product title, price, inventory, or featured image? | Shopify                      |
| Which testimonials or FAQ records exist?                        | Shopify metaobjects          |
| Where does the testimonial section appear?                      | Nyxel template               |
| How many columns and which color scheme does it use?            | Nyxel component settings     |
| Which metaobject list feeds it?                                 | Nyxel dynamic-source binding |

This division avoids synchronization work and gives an author one clear place to change each kind of information.

## Metaobjects

Shopify metaobjects are a good fit for reusable structured records. A metaobject definition can represent a testimonial, feature, store location, size guide, or campaign record. Nyxel can then bind a compatible component setting or repeater to the route’s resolved metaobject data.

The component contract should express the presentation it needs, not mirror the entire remote schema. For example, a testimonial card might accept quote, attribution, and portrait settings. The binding layer maps those settings to fields on the selected metaobject.

## Future authoring support

The runtime already supports explicit source paths and resource-shaped values. Future platform work can add richer metaobject discovery, field-aware pickers, and safer list previews while keeping Shopify authoritative.

Nyxel does not need a parallel content-model designer to provide those improvements. The editor can surface Shopify definitions and let the component contract determine which fields are compatible.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).