This guide is for marketing and digital leads, product owners and CTOs planning a new website, a portal or a move to another platform. It belongs to Netbase's web application development work, where the content model is agreed before templates, integrations and editor screens are built.
In this guide
- What is a content model, and why does it come before the CMS?
- Which decisions does a content model settle before the CMS demo?
- How do you run a content modelling workshop?
- Which CMS style fits which content model?
- When is a detailed content model not worth it?
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: other ways to start a CMS project
- Limits of this guide
- Frequently asked questions
- Next step
What is a content model, and why does it come before the CMS?
A content model is the written structure of what an organisation publishes: the content types (for example product, case study, location, person, event), the fields inside each type and the relationships between types. It describes content as data, separate from how any page looks.
It comes first because every CMS stores content in its own way, and the model is the yardstick. A model with a handful of page-like types fits almost any CMS. A model with many linked types, several languages and more than one channel quickly separates the products that handle references, localisation and APIs well from those that do not.
Vendors that publish modelling guides say the same thing in different words. Contentstack advises teams to think in content types, not web pages, so the same entry can appear on a website, an app or another channel. Contensis lists types, fields, metadata, taxonomy and relationships as the parts of a model.
Which decisions does a content model settle before the CMS demo?
A finished model answers five questions that a CMS demo cannot answer for you:
- What is reused. If a product description appears on a product page, a comparison table and a partner portal, it is one entry with one owner, not three copies.
- What is structured and what is free text. A field such as price note, region or audience can drive filters and search; a body field cannot.
- How types connect. A case study links to a service, an industry and a product; the number of links on each side (one-to-one, one-to-many, many-to-many) is where CMS products differ most.
- What changes per language or per brand. Some fields are translated, some are shared, and some differ per market or per store.
- Who owns each type. An owner per type decides who edits, who approves and who retires stale entries.
How do you run a content modelling workshop?
Netbase runs the model as five short working sessions with the people who write, approve and build. Each session has one written output.
-
Inventory
Collect the pages, documents and data you publish today and plan to publish next. Group them by what they are, not by where they sit in the menu. Output: a list of candidate types with three real examples each.
-
Types
Merge candidates that share the same fields and split those that behave differently. A design variation is a template choice, not a new type. Output: an agreed short list of content types, each with a one-line definition and an owner.
-
Fields
For each type, write every field with its kind (short text, rich text, number, date, media, reference, list), whether it is required, whether it is translated and an example value. Output: a field dictionary.
-
Relationships
Draw how types link and write the direction and cardinality of each link: a case study has one client and many services; a service has many case studies. Output: a relationship diagram and the rules for orphaned entries.
-
Editor test
Enter real content for the three most used types in a spreadsheet or a throwaway prototype and ask editors to complete everyday tasks: publish, update, translate, retire. Fix what breaks. Output: a tested model and a list of open decisions with an owner each.
The outputs become the CMS shortlist criteria and, later, the acceptance criteria for the build. Hygraph describes the same habit of testing a model with editors before frontend code is written, and warns that a model split into too many small pieces becomes hard for editors to use.
Which CMS style fits which content model?
The model does not choose a product, but it narrows the style of CMS. Use this matrix after the editor test.
| Model trait | Coupled CMS (pages and templates in one system) | Headless CMS (content through an API) | Custom admin on a web framework |
|---|---|---|---|
| Few types, mostly pages, one website | Usually the simplest fit | Often more than needed | Rarely worth it |
| Many linked types and reused entries | Works if references and custom fields are strong | Strong fit; check reference depth and query limits | Fits when rules are specific to the business |
| Several languages, brands or stores | Check per-field translation and per-site settings | Check locale fallback and per-space governance | Fits when markets need different workflows |
| Content feeds an app, a portal or other systems | Possible through plugins or an API layer | Strong fit by design | Strong fit; you own the API |
| Content is tied to transactions, accounts or approvals | Weak beyond simple forms | Needs a separate application anyway | Usually the right home |
Two decision rules help. If a type carries business rules (who can see it, what happens when it changes), treat it as application data in a custom admin, not CMS content; our portal requirement checklist covers that side. If editors mostly change page layout rather than structured entries, a coupled CMS with good templates beats a headless one. Our comparison of headless and traditional commerce platforms applies the same trade-off to online stores.
When is a detailed content model not worth it?
Skip the full workshop when the site is a brochure of a few pages with no reuse, one language and one editor; a page list and a template list are enough. Keep it light when the CMS is a hosted tool whose structure you cannot change; model only the parts you can configure. And do not model for channels you have no plan to build: every extra type and field is something editors must fill and someone must maintain.
Where AI fits
AI tools speed up the inventory session: grouping hundreds of existing pages into candidate types, proposing field lists from sample entries and flagging near-duplicate content. An engineer and the content owner still decide every type and field, because a tidy proposal can merge two types that behave differently. Netbase works with the major commercial and open-source AI tools and models, chosen per project, under human control.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online printing store; it is not a content modelling tool.
- Available capability
Content inventory clustering
Candidate types and field lists drafted from existing pages and reviewed by people; not yet tied to a published case.
What delivery record exists, and what does not
Netbase has delivered commerce and web platforms on WooCommerce, Magento 2, Laravel and headless commerce, and several of those projects were built on a structured model with many linked types.
For a Dubai-based loyalty and rewards technology company that is not named, Netbase delivered a headless multi-store reward shop platform on Magento 2 Open Source with a Next.js front end: individually branded reward shops per client programme, Arabic and English, and catalogue and ordering data synchronised with the client's own systems. For a founder launching a bilingual English and Nepali classifieds marketplace, Netbase delivered requirements, wireframes and a Laravel backend with REST APIs, category and location search and multi-language SEO. For Deyar Printing & Advertising in Riyadh, Netbase (Printcart) built a bilingual Arabic and English web-to-print platform on a Laravel headless commerce foundation across seven product families.
Netbase's delivery lifecycle starts with discovery and strategic alignment, which is where a content model is agreed. Teams combine business analysts, project managers, solution architects, developers, QA and UI/UX designers. In custom development, the client owns the IP created for it, including the model and admin screens built for the project.
Netbase does not publish a content modelling case study, an editor productivity figure or a migration result. This guide explains a method; it is not a case study.
Alternatives: other ways to start a CMS project
- Choose the CMS first and fit content to it. Fits a small site with standard pages and a team that already knows one CMS well; the risk is discovering missing references or translation rules after launch.
- Design pages first, model later. Fits a campaign site with a short life; for a long-lived site it hard-codes layout into content and makes reuse expensive.
- Copy the old site's structure. Fits a like-for-like move with no new channels; it carries old duplication into the new platform.
- Hire an agency for one platform. Fits when the platform is already decided; read our guide to choosing a WordPress and WooCommerce agency for that route.
Selection criteria: model first when content is reused, multi-language, multi-brand or feeds more than one channel; choose the CMS first when none of those apply. Most Netbase projects are delivered on fixed-price contracts; milestone-based and monthly team retainer models are also offered, and a written model makes a fixed scope easier to agree. If the site must also install as an app, check the PWA platform limits first.
Limits of this guide
- It covers the structure of content, not visual design, editorial workflow, member sign-in and roles or the migration of existing entries.
- It does not compare named CMS products; use the model to run that comparison against your own needs.
Plan the next step with a Netbase consultant
Frequently asked questions
It depends on how many content types and languages you have. A small site can agree its model in a few sessions, while a multi-brand or multi-language platform needs more rounds of editor testing before the model is stable.
The people who write and approve content, the owner of each content type, a solution architect or developer who will build the CMS, and someone who knows the integrations. Without editors the model fits the code; without developers it ignores what the CMS can do.
Yes, but adding a field is cheap and changing a type or a relationship is not, because every existing entry, template and integration that uses it must move too. That is why the relationships are tested before the CMS is chosen.
No. A model with few types and one website often fits a coupled CMS best. Headless pays off when the same entries feed several channels or front ends.
Next step
If you are about to choose or replace a CMS, tell us about your content and channels and we will reply with a proposal for a content modelling workshop and a CMS fit review.
Related services and solutions
Web application development with AI built in where it converts Netbase provides web application development for product and commerce teams that need fast, maintainable web apps and storefront front ends, with AI search, assistants and automation added where they measurably help. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to its published case studies, PrintLeo's page load improved 35% and 4over4's conversion rose 48%.
Learn More
Digital product accelerators for SaaS, mobile and AI products Digital product accelerators are Netbase-built modules and delivery patterns that help founders and product teams launch SaaS, mobile and AI products faster. Instead of rebuilding accounts, billing, workflows and integrations from scratch, you reuse proven components, spend engineering time on what makes your product different, including the AI features buyers now expect, and own the custom code built for you.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.