Content Modeling and Taxonomy Design
Content modeling defines reusable content types, their fields, constraints, and relationships. Taxonomy design supplies controlled concepts and labels so people and systems can classify, find, filter, and reuse that content consistently.
itWeb development | OpenSkills.info
Intro
Content Modeling and Taxonomy Design
Content modeling defines the structure of reusable content. A model names the content types in a domain, the fields each type carries, the constraints on those fields, and the relationships between types. Taxonomy design defines a controlled set of concepts for classifying that content. Together they turn pages and documents into structured records that people can create consistently and software can query reliably.
Two structures with different jobs
A content model describes what a record is made of. For an article, the model might require a title, summary, author reference, body, publication date, and topic references. The model controls the shape and validity of every article record.
A taxonomy describes what a record is about or how it belongs in a collection. A topic concept can have one preferred label, alternative labels, a broader concept, narrower concepts, and related concepts. The record refers to the concept's stable identifier instead of storing an uncontrolled label.
Keep these structures separate. Article is a content type. Network security is a taxonomy concept. A field such as topics connects them. Mixing types and topics produces ambiguous schemas and categories that are hard to govern.
Architecture and content flow
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.sanity.io/content-modeling
Supports
- Content modeling as defining content types, attributes, and relationships
- Structured content as presentation-independent parts that can be reused across channels
- Conceptual domain modeling before implementation schema details
- https://www.sanity.io/docs/apis-and-sdks/introduction-to-schemas
Supports
- Schemas as definitions of content structure, relationships, and constraints
- JavaScript or TypeScript schema configuration and generated types
- https://www.contentful.com/help/content-models/
Supports
- Content models as sets of content types
- Reference fields linking content types
- Visual and API-driven model implementation
- https://www.contentful.com/help/fields/
Supports
- Field types, validations, references, and field settings in a content model
- https://www.w3.org/TR/skos-primer/
Supports
- Concepts with stable identifiers, labels, notes, semantic relationships, and concept schemes
- Preferred, alternative, and hidden label roles
- Broader, narrower, related, and mapping relationships
- SKOS as a representation model for knowledge organization systems rather than a formal ontology language
- https://www.w3.org/TR/skos-reference/
Supports
- Normative SKOS classes, properties, integrity conditions, and inference behavior
- At most one preferred label per language for a concept
- Semantic relationship and mapping property distinctions
- Historical SKOS namespace information
- https://www.dublincore.org/resources/metadata-basics/
Supports
- Shared metadata terms and application profiles
- Dublin Core element purposes and its 1995 origin
- https://www.dublincore.org/specifications/dublin-core/
Supports
- Dublin Core publication and standardization milestones from 1995 through 2019
- DCMI Metadata Terms maintenance
- https://www.dublincore.org/workshops/dc-1/
Supports
- Dates, participants, purpose, and legacy of the first Dublin Core workshop
- https://www.w3.org/press-releases/1999/rdf/
Supports
- RDF Recommendation date and role as a model for organizing web metadata
- https://www.w3.org/standards/history/skos-reference/
Supports
- SKOS Recommendation publication date
- https://schema.org/docs/datamodel.html
Supports
- Schema.org types, properties, inheritance, and expected value types
- https://schema.org/docs/about.html
Supports
- Schema.org as a shared vocabulary founded by major search providers
- Schema.org launch in 2011
- https://schema.org/docs/howwework.html
Supports
- Schema.org release and consensus process since 2011
- https://www.w3.org/standards/history/json-ld/
Supports
- JSON-LD Recommendation publication date
- https://github.com/sindresorhus/awesome
Supports
- Discovery of curated Content Management Systems awesome lists
- https://github.com/nirgn975/awesome-drupal
Supports
- Drupal ecosystem tools, modules, documentation, and learning resources
- https://github.com/directus-community/awesome-directus
Supports
- Directus ecosystem resource discovery
- https://github.com/DanailMinchev/awesome-payload
Supports
- Payload documentation, examples, templates, and plugins as a curated ecosystem
- https://www.drupal.org/docs/user_guide/en/structure-taxonomy.html
Supports
- Drupal vocabularies, taxonomy terms, hierarchy, and content classification
- https://www.drupal.org/docs/administering-a-drupal-site/managing-content-0/working-with-content-types-and-fields
Supports
- Drupal entity types, bundles, reusable fields, sorting, grouping, and filtering
- https://directus.com/docs/getting-started/data-model
Supports
- Directus collections, fields, and relationships
- https://payloadcms.com/docs/configuration/collections
Supports
- Collections as records sharing a schema
- Fields generating stored document structure and APIs
- https://payloadcms.com/docs/fields/overview
Supports
- Payload field types, relationships, validation, and administrative descriptions
- https://docs.strapi.io/cms/features/content-type-builder
Supports
- Collection types, single types, reusable components, fields, validation, and relationship cardinalities
- Field rename migration risk
- https://www.contentstack.com/docs/developers/create-content-models
Supports
- Contentstack content types and structured templates
- https://www.contentful.com/pricing/
Supports
- Contentful free and paid plans
- Visual modeler, reference fields, taxonomy, localization, and governance capabilities
- https://www.sanity.io/pricing
Supports
- Sanity free and paid hosted plans
- Content platform and Studio capabilities
- https://github.com/sanity-io/sanity
Supports
- Open-source Sanity Studio code and license
- https://www.contentstack.com/pricing
Supports
- Contentstack commercial plans and content-modeling capabilities
- https://www.storyblok.com/pricing
Supports
- Storyblok free and paid plans
- Component schemas and visual editing capabilities
- https://hygraph.com/pricing
Supports
- Hygraph free and paid plans
- Models, components, locales, GraphQL APIs, and taxonomy capabilities
- https://strapi.io/pricing
Supports
- Strapi hosted plan options and commercial features
- https://github.com/strapi/strapi
Supports
- Open-source Strapi community code and license
- https://directus.com/pricing
Supports
- Directus cloud and self-hosting plan options
- https://directus.com/bsl
Supports
- Directus Business Source License conditions
- https://payloadcms.com/posts/blog/open-source
Supports
- Payload open-source licensing and free self-hosted software
- https://www.drupal.org/about/licensing
Supports
- Drupal open-source GPL licensing
- https://business.adobe.com/products/experience-manager/adobe-experience-manager.html
Supports
- Adobe Experience Manager content modeling, fragments, assets, and multichannel delivery
- Commercial sales-led availability
- https://www.sitecore.com/products/content-management
Supports
- Sitecore content types, fields, taxonomy, localization, and enterprise content management
- Commercial sales-led availability
- https://github.com/sindresorhus/awesome#content-management-systems
Supports
- Relevance of Drupal, Directus, and Payload ecosystem lists to content management
