Content modeling defines the structure, hierarchy, and relationships of content, while a CMS stores and manages it.Rather than replacing each other, they work together to turn a plan into a working system. First, clarify what content the website needs and how its elements should be organized, then map that structure to the CMS’s input fields. A clear structure helps content display correctly on the website, but traditional and headless CMSs handle presentation differently.
Content modeling clarifies content, not just layout
According to Tenten’s 2023 article, content modeling defines the structure and hierarchy of different content types and the relationships between them. This includes distinguishing between content such as blog posts and buttons. The focus is not simply on where elements appear on screen, but on first understanding what each represents and how they come together to form the website’s content.
Consider the text, images, and calls to action (CTAs) mentioned in the article. During planning, you can clarify what each is for and map it to CMS fields, rather than treating an entire page as one indivisible block of content. This helps keep website design and content management consistent in how they structure content. Three questions can guide this planning:
- Content types: What different kinds of content does the website need to manage?
- Structure and hierarchy: What elements does each piece of content contain, and how are they organized?
- Relationships: How are different content types connected?
A CMS manages content but does not necessarily handle front-end presentation
A CMS is a platform for storing and managing content. Tenten’s 2023 article notes that most CMSs provide fields for entering content. When a website is well structured, the images and CTAs entered, along with the text formatting applied, can display appropriately on the site. Installing a CMS does not mean content structure can be ignored; how its fields work with the website still matters.
Tenten’s 2025 introduction makes a further distinction: a traditional CMS typically handles both content management and page display, while a headless CMS focuses on content data and APIs, leaving developers to build the website’s visual interface. In other words, managing content and displaying it can be separate responsibilities. Not all CMSs are the same kind of website-building tool.
Identify content needs first, then check whether the CMS can support them
To make content modeling and a CMS work together, start with a content plan. Tenten’s 2023 article recommends considering both short- and long-term content needs and bringing content creators, designers, and developers together to discuss the website’s scale and how the team will update its content over time.
At Procrustes, for example, our services cover page planning, design, and functionality development for partner websites, as well as content topic planning, writing, and updates.
When choosing a system, Tenten’s 2025 article suggests checking whether you can customize content structures, which APIs are supported, and how easily the team can use the system and collaborate. Also assess whether it meets your multilingual, cross-platform, and deployment needs. For example, if content needs to be delivered to different front ends, API support is worth comparing. If multiple people will maintain the content, the interface and collaboration capabilities should also be assessed. These are selection criteria, not a suggestion that every project needs every feature.
Content modeling and CMSs: perspectives from across the web
Can a CMS help track content performance?
Some CMSs can track button or link clicks, such as clicks on links from social media posts to a website, helping teams optimize content and track conversions across platforms. However, only some systems offer this capability; it should not be assumed that every CMS does. If performance tracking is a requirement, confirm during selection that the system supports the tracking methods you need.
How does website size affect platform choice?
When choosing a platform, consider both short- and long-term content plans. Using a website that publishes blog posts weekly as an example, the 2023 article recommends choosing a website builder that supports more than 20 pages. If the site contains only basic information or a few longer blocks of text, 20 pages may be enough. This is an example of assessing content needs, not a threshold that applies to every website.
What should you look for in API support when choosing a headless CMS?
Check the system’s support for REST and GraphQL, and compare them based on your project’s needs. The 2025 selection guide suggests that supporting both can make it easier to integrate with different front-end frameworks later. However, this is a comparison criterion, not a requirement for every project to use both API types. Also weigh the flexibility to customize content structures, ease of use for the team, and pricing.
References
- 什麼是 Headless CMS? 無頭 CMS 懶人包: 開發者和行銷必看的神器tenten.co · 2025-08-28T02:32:38.000Z — Discusses: What should you look for in API support when choosing a headless CMS?
- 網站內容建構必備知識與概念tenten.co · 2023-08-07T11:12:05.000Z — Discusses: Can a CMS help track content performance?; How does website size affect platform choice?
