A content management system (CMS) separates the job of creating and organizing content from the job of writing code. Instead of hand-editing HTML files, site owners log into an administrative dashboard, type content into forms, and the platform stores it in a database and renders it through templates. This single idea underpins a large share of the modern web, and it explains why so many professional web projects begin with the question "which CMS?" rather than "which framework?"
The platforms in this topic occupy different points on a spectrum. WordPress dominates by market share and plugin ecosystem; Joomla sits in a flexible middle tier; Drupal targets enterprise and government sites with complex content models and permissions; Shopify specializes in e-commerce; Wix and Squarespace bundle hosting, templates, and editing into a single hosted service; and headless CMS platforms strip away the front end entirely, delivering content through APIs to whatever application consumes it. Each choice trades control against convenience, and cost against capability.
The videos below approach the topic from the comparison angle and from the headless angle. As you watch, build a mental table: who is the intended user, what technical skill is assumed, where does the content actually live, who hosts it, and what happens when the project grows or the requirements change. Pay particular attention to the arguments made for traditional CMS platforms as well as against them—being able to argue both sides is the point of this module, not picking a favorite.
A comparison video that surveys the main categories of site-building tools—no-code builders, headless CMS platforms, and traditional CMS platforms—using named products including Framer, WordPress, Webflow, Wix Studio, and Shopify as examples. Based on its title and description, it is organized around which platform category fits which kind of project rather than around tutorials for any one tool. Expect discussion of trade-offs such as ease of use, flexibility, and e-commerce versus general content needs.
This is the broadest single match for the topic, touching the hosted-builder, e-commerce, traditional, and headless subtopics in one pass, which makes it a useful framing video before the deeper headless material.
This video explains what a headless CMS is and, equally important, who it is not for. The description signals a deliberately non-hyped treatment that argues traditional CMS platforms remain the better choice for many projects, so expect the limitations of decoupled content delivery alongside its benefits. It should help you connect the architecture to realistic use cases.
It directly serves the headless CMS subtopic while also supporting the "choosing the right CMS" subtopic by resisting the common assumption that newer equals better—exactly the balanced reasoning this module asks for.
A fundamentals-level explanation of headless architecture as a general approach to building and deploying systems, with customer engagement and eCommerce platforms as the motivating examples. It focuses on the underlying architectural concepts—separating the content or commerce back end from the presentation layer—rather than on a specific vendor's product. This gives you the technical vocabulary behind the term "decoupled."
From a channel devoted to headless architecture, it supplies the conceptual grounding that the shorter comparison videos assume, and its eCommerce framing links the headless subtopic back to Shopify and e-commerce platforms.
Together these videos build the comparative foundation MO1 requires: the first surveys WordPress, Shopify, hosted builders, and headless options side by side, while the second and third go deeper on decoupled architecture so you can weigh it against traditional and custom approaches. The repeated emphasis on "who is this for" and "when does the traditional option still win" models the structured decision-making MO2 asks you to perform, giving you criteria—scope, technical capability, scalability, and cost—to justify a platform recommendation for a client scenario. The videos do not address webmaster operations, maintenance planning, or client communication (MO3 through MO5); those outcomes are covered by the module's readings and assignments, though the platform differences discussed here directly shape what update, backup, and security work a site will later demand.
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.