A companion set of open-ended discussion questions for all eight lessons of the course — designed for classrooms, study groups, reading circles, and team workshops. There are no single right answers here; each prompt is meant to spark debate, reflection, and the application of ideas to real situations.
In a classroom: assign a lesson as reading, then work through 4–6 questions as a group. Questions build from recall toward judgment and application.
In a study group: let each member champion a different question and lead the conversation.
On a team: use the prompts tagged Apply to connect the ideas directly to your own CMS, content, and processes.
The course claims content management is "older than the Web" and points to the Library of Alexandria. What do a modern CMS and an ancient library genuinely have in common — and where does the analogy break down? Analyze
Content is defined by two properties: creation through editorial process, and intention for human consumption. Can you think of something that has one property but not the other? Is it content? Debate
"Content is never 'right,' it's just 'right now.'" Do you agree that all content is perpetually provisional, or are there kinds of content that are genuinely "finished"? Debate
The distinction between content and data is said to be defined by the services we apply, not the information itself. Take one piece of information from your own life and argue it could be either. Apply
Why does the course insist on separating the discipline of content management from any particular software? What is gained by holding that distinction firmly?
If there is "no Grand Unified Theory of Content Management," how should a newcomer decide which best practices to trust? Debate
Of the four things a CMS does — control, reuse, automation/assembly, editorial efficiency — which would matter most to a small nonprofit? To a global news organization? Why the difference? Apply
The course lists four things a CMS does not do (create content, make marketing plans, format well, provide governance). Which of these failures do you think derails the most projects, and why?
Some clients called years after launch asking how to log in for the first time. What organizational failures lead to a brand-new CMS never being used?
In the homebuilding analogy, "you" are the prime mover, not the tools. Where in your own experience have people mistaken the tool for the outcome? Reflect
"A CMS is a means to an end, never the end itself." How would you explain this idea to an executive who wants to buy a top-rated platform to "fix the website"? Apply
Editorial morale is called "intangible but critical." How much should the feelings of the people using a system influence which system an organization chooses? Debate
The "big four" (WCM, ECM, DAM, RM) each excel at something different. If a single organization needed all four strengths, would you advise one blended system or four specialized ones? Apply
DAM is said to be defined by what it does to assets rather than what it stores. Is a category defined by its processes more or less useful than one defined by its content? Debate
The lines between CMS types are "blurry," and systems get classified by market, community use cases, and features. Is this classification helpful to buyers, or does it mislead them?
"Enterprise" is described as a vague term that often just means "expensive." Where else in technology do you see vocabulary used more for positioning than precision? Reflect
"All software is opinionated; the only question is how strong those opinions are." Do you find this liberating or troubling as a future buyer of software? Debate
Your affection for software is "directly proportional to how closely its opinions line up with yours." How can a buyer discover a system's true opinions before committing to it?
The "list of pages" example shows a set of built-in opinions that satisfies most customers. When is it wise to accept a system's defaults rather than customize? Apply
"Requirements settling" — changing your use case to fit the software — is called more common than people admit. Is this pragmatic wisdom or quiet defeat? Debate
Some customers want software to enforce its opinions and treat a product as "hard-won consulting." When is outsourcing your methodology to a vendor a good idea?
Strongly-opinionated software "thrives in industry verticals" like museum collection management. What field that you know well would benefit from a strongly-opinionated tool? Apply
The market trend is toward generalized platforms with "fewer opinions." Do you expect that trend to continue, or will AI push things back toward opinionated, do-it-for-you tools? Debate
Drupal (a WCM) gets used for enterprise content and Documentum (an ECM) for websites. What are the risks of using a tool far outside its intended category?
Reification is "making the abstract concrete." Why is turning a fuzzy human idea into rigid fields one of the hardest parts of building any content system? Analyze
The street-address example shows structure trading flexibility for capability. Describe a piece of content where you'd deliberately choose less structure. Apply
An attribute turns out to have many hidden parts (value, name, label, datatype, editorial element, validation). Why is it valuable for even non-technical editors to know this? Reflect
Internal attribute names are often unchangeable once set. What discipline does that impose on the people first designing a model?
"A type contains no data." Why is it important to insist that all data lives in attributes and a type is merely a wrapper?
The distinction between an attribute type and an attribute assignment is subtle. Why does "Title on Article" need to be treated as different from "Title on Employee Profile"? Analyze
The cookie-cutter analogy separates the pattern (type) from the instance (object). Where else in software or life do you see the same pattern-vs-instance idea? Reflect
The course jokingly proposes calling content types "Platonic Forms." Does philosophical framing help you understand modeling, or does it overcomplicate a practical task? Debate
Two types with identical attributes are "functionally the same type." When, if ever, is it worth duplicating a type purely for a different name (e.g. Article vs. Blog Post)? Debate
Modeling mistakes "reverberate for the entire life of your system." How should a team balance careful up-front modeling against the need to ship something?
Sketch a content type for a recipe. What attributes would you include, and which datatype would each use? Apply
If you had to teach the type-vs-object distinction to someone in one sentence and one example, what would you say?
"Content almost always exists in relation to other content." Can you think of any content that is genuinely standalone, with no meaningful relationships? Debate
Relationships range from explicit reference attributes to implied co-membership in a category. Which kinds are most fragile, and why do they break? Analyze
Why is referential integrity — not deleting something others depend on — harder to maintain as a content collection grows?
The five shapes are serial, hierarchical, tabular, network, and relational. Pick a website you use often and identify the shape of each major section. Apply
WordPress excels at serial content but struggles with hierarchy; MediaWiki is the reverse. Why do tools become so specialized to a shape? Analyze
"Almost any system can be contorted to work with any shape" — but at the cost of heroic effort or a confusing editor experience. When is that cost worth paying? Debate
A single site usually mixes several shapes. What problems arise when one CMS must serve hierarchical, tabular, and serial content at once? Apply
Josh Clark warns that heavy structure "forces editors to approach their content like machines." Where's the line between helpful structure and dehumanizing rigidity? Debate
The course warns that over-modeling is as real a failure as under-modeling. How would you recognize that a model has become too granular?
Requirements should drive granularity, "not hypothetical future ones." How do you resist the temptation to model for imagined future needs? Reflect
Consider a restaurant's website. Which relationships between content objects (menus, dishes, locations, staff) would you model explicitly? Apply
If your content's shape and your CMS's strengths disagree, is it better to switch tools or adapt your model? What factors decide?
The lifecycle (create → edit → approve → publish → archive → delete) is "not a straight line." Trace a realistic path a piece of content might actually take, with loops and detours. Apply
A single object can be published, in draft, and archived all at once. Why is this "layers of visibility" idea confusing for newcomers, and how would you explain it?
Five roles surround a CMS (editors, site planners, developers, administrators, stakeholders). Which role's needs do you think get neglected most often, and why? Debate
"'Editor' is a crude generalization." Why does treating all editors as one undifferentiated group cause problems?
Versioning enables rollback, audit, and comparison. Which of these matters most in a regulated industry like finance or healthcare? Apply
Scheduling and expiration automate publishing and retirement. What could go wrong if a large site relied heavily on automatic expiration? Analyze
The course distinguishes workflow (movement) from permissions (authorization). Why is conflating the two a common and costly mistake?
Teams often ask for "workflow" when they really want "collaboration." How would you diagnose which one a team actually needs? Apply
"Rigid approval chains can get in the way of the informal back-and-forth that makes content good." When is heavy process genuinely worth the friction? Debate
Permissions are granted through roles and groups rather than individually. What are the trade-offs of role-based access versus per-person control? Analyze
Dependency management surfaces "orphaned" content. Why does unused, unreferenced content accumulate, and whose job is it to prune it? Reflect
Design a minimal approval process for a five-person team's blog. What is the fewest number of steps you can justify? Apply
Separating content from presentation lets one source feed many channels. What is the hidden cost of that separation, in effort or complexity? Analyze
Content, artifact, and channel are carefully distinguished. Take a single article and describe three different artifacts it might become. Apply
Because content is "write once, read many," heavy investment in delivery pays off. Where else does the WORM principle justify up-front effort? Reflect
Templating languages are deliberately less powerful than full programming languages. Why would a system intentionally limit what template authors can do?
"The surround" is everything on a page outside the operative content object. Why is separating the surround from the content object such a useful idea? Analyze
The course claims "truly understanding a CMS often means understanding how it aggregates." Why would aggregation, of all things, be the deepest test of a system? Debate
Aggregations vary along many axes (static vs. dynamic, manual vs. derived ordering, etc.). For a homepage "featured" section, which settings would you choose? Apply
"Organizing content often creates content." Do you agree that a curated list deserves the same management (versioning, permissions) as the items it groups?
The "tyranny of the tree" describes too much functionality bound to one hierarchy. Have you seen a system where one structure controlled too much? Reflect
When the same content must appear in two places in a tree, systems use a "main" location plus a reference. What problems can this create for editors? Analyze
Content is consumed inside "cognitive containers" like pages or app screens. How does designing for the container change how you model the pieces? Apply
As delivery spreads across web, email, app, and voice, does the classic "page" remain a useful unit — or is it becoming obsolete? Debate
Every CMS has a management side and a delivery side. Why is the relationship between these two the "most significant" architectural decision? Analyze
In a coupled system, publishing is "almost anticlimactic" — just flipping a flag. In a decoupled one, it means moving data. How does that change how teams think about "going live"?
Compare coupled, decoupled, and headless in your own words. Which would you default to for a brand-new small business site, and why? Apply
The default architecture swung decoupled → coupled → decoupled again. What does this reveal about how technology trends actually move? Reflect
"Vendors move in packs" as external technology shifts. Is this herd behavior good or bad for customers? Debate
Decoupling can improve security by shrinking the delivery server's attack surface. How much should security concerns alone drive an architecture choice? Debate
Decoupling lets you avoid licensing a CMS on every delivery server. When do cost savings like this outweigh the added operational complexity? Apply
Headless "waits to be pulled" rather than "pushing" content out. What kinds of projects most benefit from that inversion of control? Analyze
A bank's custom platform can't be "owned" by a CMS, forcing the CMS to be subservient. Where else might content be secondary to a system's primary purpose? Apply
The deciding question is "how many channels must you serve?" Is channel count really the best single predictor of the right architecture? Debate
The course warns against buying "architectural complexity you don't need." How can a team tell the difference between future-proofing and over-engineering?
If headless maximizes flexibility but requires building your own front end, who should not choose headless? Apply
A CMS ecosystem (developers, integrators, docs, community) is called a "core feature." How would you actually evaluate the health of an ecosystem before buying? Apply
"There is no soulmate for your project, and all that glitters will eventually lose its shine." How do you set realistic expectations without becoming cynical? Reflect
The selection process is a "funnel of deepening analysis." What criteria belong at the wide top of the funnel versus the narrow bottom? Analyze
Out-of-the-box functionality is often "illusory." Why do buyers keep falling for the OOTB promise despite repeated disappointment? Debate
"Poor governance and vague ownership do far more damage than a lack of technology." Do you agree that people problems outweigh tool problems? Debate
"Software is not your savior." How would you push back on a leader who believes a new platform will fix a struggling website? Apply
Developers are famously drawn to building a CMS, but the course says resist. When, if ever, is building your own genuinely justified?
Migration is called maybe "the most dangerous word in CMS." Which of its phases (extract, transform, reassemble, import, resolve, QA) seems riskiest to you, and why? Analyze
"Content velocity" means content keeps changing even while you migrate. How would you manage a migration of a site that never stops publishing? Apply
CMS software is described as very "sticky." Is high switching cost a sign of a good investment or a trap to avoid? Debate
"Launch day is not the finish line, it's the starting line." What ongoing commitments does an organization take on the day after launch? Reflect
Among the predicted trends (consolidation, decoupling's return, marketing focus, SaaS at the low end, multichannel, distributed intake), which do you find most convincing today, and which has aged poorly? Debate