content-modelling

Design structured content models for multi-channel publishing and CMS architecture.

10|2|Updated Mar 12, 2026

Search Tags:#cms #content-types #content-modeling #relationship-mapping #field-design

Ready to run

npx skills add https://github.com/viktorbezdek/skillstack --skill content-modelling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-modelling
Source: https://github.com/viktorbezdek/skillstack/tree/main/content-modelling/skills/content-modelling
Command: npx skills add https://github.com/viktorbezdek/skillstack --skill content-modelling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Many teams struggle to define structured, reusable content models that work across multiple channels, leading to duplicated effort, inconsistent editorial workflows, and poor content governance.

Core Features & Use Cases

Content Type Blueprint: Template for defining purpose, cardinality, and lifecycle of each type.
Field Catalog: Standardized field definitions (short text, rich text, media, reference, enum, etc.).
Relationship Modeling: Guidance for reference, embedded, and hierarchical connections.
COPE Principles: Strategies to create once and publish everywhere, supporting multi‑channel delivery.
Anti‑Pattern warnings: Helps avoid page‑based models, embedded HTML, and monolithic types. Use case example: designing a blog post type with title, slug, body, author reference, and publication status for a headless CMS.

Quick Start

Ask the content-modelling skill to generate a complete content type definition for a blog post.

Frequently Asked Questions about content-modelling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design structured content models for multi-channel publishing?▼

Structured content models for multi-channel publishing are designed by defining content types, field specifications, relationships, and validation rules based on COPE principles. This approach ensures content reuse across platforms and prevents duplicated effort in your CMS architecture.

What are common anti-patterns to avoid when creating content type definitions?▼

Common content type definition anti-patterns include page-based models, embedded HTML, and monolithic types. Avoiding these ensures your content remains structured, reusable, and governed properly across different editorial workflows and delivery channels.

How do I map relationships and references in a headless CMS?▼

Relationship mapping in a headless CMS involves defining reference, embedded, and hierarchical connections between content types. Proper relationship modeling ensures structured data integrity and supports multi-channel delivery without duplicating underlying content.

What is the best way to define a field catalog for content reuse?▼

The best way to define a field catalog for content reuse is to use standardized field definitions including short text, rich text, media, reference, and enum types. This standardization enforces validation rules and supports consistent editorial workflows.

Can I apply COPE principles to existing editorial workflows and CMS architecture?▼

COPE principles can be applied to existing editorial workflows and CMS architecture by restructuring content into reusable models. This involves creating content type blueprints that define purpose, cardinality, and lifecycle to support multi-channel delivery.