--- title: "Content type" description: "A category of content with a defined purpose and structure, such as a case study or an event." category: "Structure and systems" canonical: "https://contentlexicon.com/content-type" updated: "2026-10-11" --- # Content type _Structure and systems_ > A category of content with a defined purpose and structure, such as a case study or an event. A content type is a defined kind of content with a consistent purpose and structure: an event, a case study, a job vacancy, a product page or a news story. Defining one means deciding which parts every item of that kind contains, which are optional, what format each takes and how it relates to other content. An event might always have a title, date, summary and booking route, with venue details for in-person events and joining instructions for online ones. Every event then follows the same pattern, however and wherever it's displayed. The idea reached content work from technical communication. IBM's DITA, published in 2001 and approved as an OASIS standard in 2005, split documentation into typed topics (concept, task and reference), each with its own structure. Web content management adopted the same thinking, and Rachel Lovinger's 2012 article in A List Apart described content types as one of the three building blocks of a [content model](https://contentlexicon.com/content-model). ## Why it matters for content Content types are how a pile of pages becomes a system. Once a type is defined, an organisation can make reliable promises about it: what it always contains, how it appears in a listing, how it behaves in search, who owns it, how often it's reviewed and when it should be retired. Authors get clearer guidance about what to write, developers get something to build against and readers get consistency they may never consciously notice. Every job vacancy shows its closing date in the same place, and every case study names the client and the outcome. A type also separates what content is from how it looks. The same event record can appear as a card in a listing, a full page and a line in a newsletter, each with its own template. That separation lets content move between channels without being rewritten, and it makes migrations less painful, because comparing fields shows which records convert cleanly and which exceptions need a decision. The hard part is drawing the boundaries. With too few types, everything ends up in a generic page with one large body field, which is flexible but tells systems nothing. With too many, authors can't tell which to choose and developers maintain near-duplicates. Lovinger's tests help: something deserves its own type when it has distinct elements, distinct functional needs or distinct organisational requirements, such as press releases that must feed a newsroom automatically. ## How AI changes the picture Defined types make content easier for machines to use. When dates, eligibility, prices and locations sit in their own fields, a retrieval system or assistant can find them without inferring them from prose, and a generated summary can be checked against the expected shape. A free-text page leaves the model to guess which of several dates is the deadline. AI can help design and populate types too. A model can propose candidate types and fields from existing content, cluster pages that share a structure and test a draft model against awkward cases, revealing for example that an event type has no way to record a rescheduled date. During a migration it can classify legacy pages by type and draft content into the right fields. People still need to decide which distinctions the organisation should maintain, and a valid record can still contain a wrong fact. ## Questions people ask **What is the difference between a content type and a template?** A content type defines what the content is and what it contains. A template defines how one presentation of it looks. One type can have several templates: a listing card, a full page and an [email](https://contentlexicon.com/email) version, for instance. **Is a content type the same as a content model?** A content type is one part of a content model. The model is the wider picture: all the types, their fields and the relationships between them. **How many content types does an organisation need?** As many as there are meaningful differences in purpose, structure or behaviour, and no more. A small programme might need separate event and speaker types, but not a new event type for every department. Test the model against real examples before settling the number, and merge types that turn out to be identical apart from their names. **Can a page belong to two types?** A record normally has one type, but a page can assemble several: an event, a speaker profile and related guidance, for example. Be clear whether you're classifying the record or the presentation. ## Learn more - [Content Modelling: A Master Skill](https://alistapart.com/article/content-modelling-a-master-skill/) – Rachel Lovinger's A List Apart article on building a content model from an assembly model, content types and attributes, with tests for when something deserves its own type. - [History of DITA](https://dita-lang.org/history) – how IBM's concept, task and reference topics grew from an internal workgroup into an OASIS standard, with a timeline of later releases. - [An introduction to structured content](https://digital.gov/resources/an-introduction-to-structured-content) – Digital.gov on publishing content as modular, machine-readable pieces, using an event that can feed a calendar, a news feed and search results as its example. Related terms: [Content model](https://contentlexicon.com/content-model), [Content pattern](https://contentlexicon.com/content-pattern), [Schema](https://contentlexicon.com/schema), [Structured content](https://contentlexicon.com/structured-content) This page was last reviewed in October 2026.