A content management system (CMS) is software that separates the content of a website from its presentation and code, allowing people who are not developers to create, edit, organize, and publish pages through an administrative interface. Behind that interface sit a few predictable parts: a database or content store, an editing and authoring environment, a templating or theming layer that controls appearance, and an extension mechanism (plugins, modules, apps) that adds functionality. Understanding these pieces is what lets you reason about any platform you encounter later, whether it is WordPress, Joomla, Drupal, Shopify, or a headless service.
This topic matters in COP4813 because the rest of the module asks you to make judgments, not just to click through dashboards. Before you can compare platforms or defend a recommendation of "CMS" versus "custom build" for a client, you need a clear mental model of how a CMS fits into the web ecosystem: where content lives, who touches it, what the server does at request time, and what parts a developer still owns. You will also meet the distinction between traditional (coupled) systems, where the CMS renders the pages it stores, and headless systems, which deliver content over an API to a front end you build separately.
The three videos below move from the general idea to two specific modern variations. While watching, keep a running list of the components each presenter mentions, note the vocabulary they use for content types and templates, and ask yourself what kind of project each approach would suit — a small brochure site, a large editorial operation, or an application front end that needs content from multiple channels.
Presented as the opening class of a WordPress course, this video explains what a content management system is before touching any specific platform. Expect a definition-level treatment: what problem a CMS solves, how it differs from hand-coding pages, and the general pieces that make up the system, framed with WordPress as the running example.
It is the natural starting point for the subtopics "What Is a Content Management System?" and "Core Components of a CMS," and its course-introduction framing keeps the explanation at the foundational level this topic needs before specific platforms are compared.
A brief, focused explanation of the headless CMS model, produced by Storyblok, a company that builds one. In about three minutes it should contrast a traditional CMS, where content and presentation are bundled together, with a headless approach where content is stored centrally and delivered through an API to any front end or channel.
Headless architecture is listed explicitly in the module outcomes, and this short piece gives you the vocabulary and the architectural contrast quickly; note that the producer is a vendor, so treat the benefits it lists as claims to verify against other sources.
An official Webflow tutorial introducing the CMS features of that platform. The description indicates it covers scaling site content dynamically and breaks down the difference between static pages and content driven by collections or structured content types, which is the practical mechanism behind templates and dynamic pages in most CMS platforms.
It makes the abstract idea of "content separated from presentation" concrete by showing structured content feeding templates, and it adds a third platform style to the comparison alongside traditional and headless systems covered in the other videos.
Together these videos build the vocabulary and mental model the module outcomes depend on. The WordPress class establishes what a CMS is and what its core components do; the headless explainer introduces the architectural alternative named directly in MO1; and the Webflow tutorial demonstrates structured content driving templates, which clarifies what a CMS automates and therefore what a custom build would require you to write yourself. That contrast is the raw material for MO2, where you will weigh scope, budget, scalability, and client technical skill to justify a CMS or custom approach. The same understanding of components, updates, and extensions also sets up the webmaster and maintenance outcomes (MO3 and MO4) later in the module, since knowing where a CMS stores content and code is a prerequisite for planning patching, backups, and content audits.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.