Almost every web project begins with the same question: do we build this on an existing content management system, or do we write it from scratch? A CMS such as WordPress, Drupal, Joomla, or Shopify gives you a pre-built administrative interface, a content database, a theming layer, and a plugin ecosystem on day one. A custom build gives you complete control over the architecture, data model, and performance profile, but you are responsible for every piece of functionality a CMS would have handed you for free. Between these two poles sit hybrid options — headless CMS platforms and code-first frameworks — that let you keep an editing interface while building the front end yourself.
This question matters in COP4813 because choosing the wrong approach is expensive and hard to reverse. The decision is rarely about which technology is "better"; it is about matching the tool to the project's scope, the available budget, the expected traffic and growth, the client's willingness and ability to administer the site, and the long-term security and maintenance burden someone will have to carry. A small business brochure site and a high-traffic application with a custom data model call for very different answers, and a professional should be able to explain why.
As you watch the videos below, listen for the decision criteria rather than the product recommendations. Note when a presenter says a tool is a poor fit and what reason they give — those negative cases are often more instructive than the sales pitch. Try to collect the criteria you hear into a checklist you could actually apply to a client scenario: scope, budget, editorial workflow, scalability, technical capability of the people who will run the site, and ongoing maintenance and security responsibility.
This video explains what a headless CMS actually is — a content backend that serves data through an API to a separately built front end — and contrasts it with a traditional, all-in-one CMS. Based on its title and description, it deliberately avoids hype and focuses on who headless genuinely suits, who it does not, and why a traditional CMS remains the better choice for many projects. Expect discussion of trade-offs in editing experience, development effort, and project fit.
Headless sits squarely between "pure CMS" and "fully custom," so it is the clearest way to see that the choice is a spectrum rather than a binary; the explicit "who it's not for" framing directly supports the evaluating-scope and client-capability subtopics.
A short, focused look at Payload, a code-first CMS used in modern JavaScript stacks, framed entirely around when it is and is not the right tool. The description points to top use cases, so expect concrete project types where a developer-oriented CMS pays off versus situations where it adds unnecessary complexity. It is a practitioner's perspective on fitting a tool to a project's requirements.
It models exactly the reasoning this topic asks for — stating use cases and anti-use-cases — and shows the developer-centric middle ground where custom code and CMS conveniences meet, which is useful for the decision framework and scalability discussions.
A long-form comparison of mainstream website builders and hosted platforms, organized around matching a tool to the viewer's situation rather than naming a single winner. Expect coverage of pricing tiers, ease of use for non-technical owners, design flexibility, and the limitations that show up as a site grows. The channel produces marketing-oriented tool reviews, so the lens is practical and client-facing.
It represents the low-code end of the spectrum that many real clients will ask about, and its emphasis on cost and ease of use gives you concrete material for the budget and client technical capability criteria in your framework.
Together these videos let you compare hosted builders, traditional CMS platforms, headless and code-first CMS options, and fully custom development, which is the comparative work described in MO1. Because each video is organized around fit — who should and should not use a given approach — they supply the raw criteria (scope, budget, editorial workflow, scalability, client skill level, and ongoing maintenance) that you will assemble into the structured decision framework required by MO2. The discussions of updates, plugin ecosystems, hosting, and long-term upkeep also preview the webmaster responsibilities and maintenance planning covered later in the module, and the client-oriented framing in the builder comparison connects to the requirements-gathering and expectation-setting skills in MO5.
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.