Learning objectives
- Identify the "big four" content management categories and what each excels at
- Recognize the blurrier categories: CCMS, LMS, portals
- Understand why the lines between types are so blurry
- Explain what "enterprise" really signals
- Grasp "opinionated software" and why it matters when choosing a CMS
Recall our definition of content from Lesson 1 — notice it never mentioned the Web. Content management is bigger than websites, so before narrowing our focus it helps to see the whole landscape.
1The "big four"
Web Content Management
Management of content primarily intended for mass delivery via a website. WCM excels at separating content from presentation and publishing to multiple channels. This is the flavor most people mean by "CMS," and the focus of this course.
Enterprise Content Management
Management of general business content not necessarily meant for mass delivery — résumés, incident reports, memos. Once called "document management." ECM excels at collaboration, access control, and file management. Heavy on management tools, light on publishing.
Digital Asset Management
Management and manipulation of rich media — images, audio, video — for use in other media. DAM excels at metadata and renditioning: images can be mass-resized, video spliced and edited right in the system.
Records Management
Management of transactional records produced as a byproduct of business — sales records, access logs, contracts. RM excels at retention policy and access control.
Almost any CMS can store an image or video, and ECM is actually very good at it. What sets DAM apart isn't storage — it's the processes it applies to assets: rendering, resizing, transforming, editing. That's why a DAM's core management features overlap heavily with ECM, with a transformation layer on top. Many DAMs are literally sold as add-ons to ECM systems.
2The blurrier categories
Component CMS
Manages extremely fine-grained content — paragraphs, sentences, even individual words — often to assemble documentation or highly technical content from reusable components.
Learning Management
Manages learning resources and student interaction. Most colleges run syllabi and the learning process through an LMS — though only some of what an LMS does is truly unique to it.
Portals
Manage, present, and aggregate multiple streams of information into one unified system — pulling content and services together in a single interface.
3Why the lines are blurry
These categories are not rigid boxes. A DAM commonly feeds a website through integration with a WCM. Some ECM systems can publish to the Web. Many WCM systems have add-ons that turn them into an LMS — or are simply used as one out of the box. Software is known largely through its intended use and its reputation, and a system gets mentally filed into a category based on three things:
- The market it promotes itself in and competes in
- The use cases and examples the user community creates and promotes
- The specific features it builds for a particular kind of content or user
CMS software is targeted at particular markets — but that has never stopped anyone from using it off-label. Drupal is known as WCM, yet organizations run internal enterprise content on it; Documentum is ECM, yet some power public websites with it.
"Enterprise" has no precise definition — it roughly means "big" or "for large organizations." There's no real opposite (few CMSs bill themselves as "provincial" or "boutique"), and nothing stops the smallest CMS from calling itself enterprise. Vendors use it to signal that a system handles lots of content or fits distributed, load-balanced, multi-data-center environments — and, quietly, to set expectations on price. "Enterprise" often just means "expensive." "Enterprise content" usually means internal content that isn't published outside the organization.
4Opinionated software
This is one of the most useful lenses in the whole field. All software is opinionated to some degree — the only question is how strong those opinions are. It's a spectrum.
Software carries the opinions of the team that built it about how it should be used. What they think is a good idea gets passed down to you. Your affection for a piece of software is directly proportional to how closely its opinions line up with yours.
Some software is a general platform on which you can build almost anything (weak opinions, wide customization). Other software is designed to do one specific thing extremely well (strong opinions, narrow customization). Neither is inherently better — it depends on the fit.
Museums have a specialized sub-genre of content management called "Collection Management." These systems are highly opinionated, and that works precisely because managing a museum collection is a well-established practice with mature patterns. When the builders' opinions reliably match the users', strong opinions make life easier, not harder.
Consider a common requirement: displaying a list of pages. A system might build in opinions like "each entry shows a title linked to its own URL, with a summary and date, an image in a standard size, ordered by publish date, paginated with navigation at the bottom." That whole list is a set of opinions — but a fairly mainstream set that would satisfy many customers. When a system's built-in opinions don't match your use case, you have three options:
- Customize the implementationUse the tools the system provides to bend it toward your needs.
- Find a different systemChoose one whose opinions match yours more closely.
- Change your use caseMore common than you'd think. In "requirements settling," a buyer accepts that the system's opinions don't perfectly match, decides it's good enough elsewhere, and adjusts their plans to fit.
Some customers want the software to enforce its opinions. Intranet management, for example, falls into very common patterns, and many intranet managers want both a tool and an opinion on how to run it. An "intranet in a box" is attractive because it promises functionality plus a suggested methodology. Many customers see vendors as experienced practitioners and treat a product as a bundle of "hard-won consulting." There's an unconscious bias that the packaged way must be correct — and that if the software doesn't do something, it probably didn't need doing.
The trend, above the very low end, is toward generalized platforms you can configure to your situation — meaning fewer opinions are usually better for flexible needs. But if your requirements genuinely match a strongly-opinionated tool's worldview, that tool can be the easier, cheaper path. Fit is everything.
🔑 Key terms from this lesson
- WCM / ECM / DAM / RM
- The big four: web content, enterprise (internal) content, digital asset, and records management.
- Renditioning
- Producing transformed variants of a media asset (resized images, clipped video) — a hallmark of DAM.
- CCMS
- Component CMS: manages very fine-grained, reusable content components.
- Enterprise
- A vague marketing term meaning "big"/"for large orgs" — often also signaling higher price. "Enterprise content" = internal, unpublished content.
- Opinionated software
- Software embodying its makers' opinions about correct use; fit depends on how well those opinions match yours.
- Requirements settling
- Accepting a system's opinions that don't perfectly match, and adjusting your plans because it's good enough overall.
Review Questions
Test your understanding. Click each question to reveal the answer.