All products

Model Contentstack content with AI

Decide which information belongs inside an entry, which deserves a shared record and how those choices affect editors and delivery queries.

Model Contentstack content with AI when the same tutor biography appears on several course pages. The cms-data-modeling-best-practices skill asks whether that biography has its own owner and update cycle. If it does, an independent entry may make sense. A note written only for the opening lesson can stay with that lesson.

The reader of a schema may be an editor, a website or both. A structure that looks elegant on paper can force an editor through five screens or require a chain of requests to show a simple card. Testing one content change and one delivery query exposes both kinds of friction.

What it does

  • Separate shared values from fields that merely have the same shape.
  • Choose between a field, group, reusable entry and reference.
  • Keep filterable information available outside free-form text.
  • Identify which values require separate translations.
  • Check how a schema change would affect older entries and consuming applications.

Install and use

  1. Give the agent a permitted schema, one example entry and an ordinary editing task. Planning needs no live changes, while applying a revision requires authorised stack access.
  2. Ask, “Where should the tutor biography live if it appears on three course pages and changes independently?”
  3. Walk through one edit and one query before agreeing on a revised model.

FAQ

Source

Made by Contentstack. Original skill: cms-data-modeling-best-practices, published on GitHub under the MIT licence.

View on GitHub