Almost no modern web project is built entirely from scratch. Instead, developers pull in third-party external libraries — pre-written, tested bundles of JavaScript and CSS such as jQuery, Bootstrap, and Chart.js — so they can focus on their own application logic rather than reinventing common functionality. This topic introduces what those libraries are, where they live, and the two ways you can bring them into a page: downloading the files and hosting them yourself, or linking to a copy hosted on a Content Delivery Network (CDN).
A CDN is a geographically distributed network of servers that stores copies of files close to the people requesting them. For this course, the practical payoff is simple: a single script tag or link tag pointing at a CDN URL gives your page a fully working library with no downloads, no file management, and often faster load times. You will also need to understand the details that make CDN links reliable in production — pinning a specific version number so your site does not break when the library updates, and using integrity (Subresource Integrity) attributes so the browser can verify the file has not been tampered with.
As you watch, pay attention to two things. First, in the CDN videos, focus on the mechanics — edge servers, caching, origin servers, and latency — because that explains why a CDN link usually outperforms a file sitting on your own server. Second, in the jQuery video, notice how the library is introduced and loaded; that is the exact pattern you will repeat for Bootstrap's CSS link tag and Chart.js's script tag, and load order will matter once libraries depend on one another.
A concise, animated explainer from ByteByteGo covering what a Content Delivery Network is and how it works, including the role of edge servers, caching, and the origin server. Based on its title and framing within ByteByteGo's system design content, it likely walks through the request path from a user to the nearest edge location and why that reduces latency.
It gives you the conceptual foundation behind the CDN subtopics in under five minutes, from a channel known for clear, accurate system-design explanations — ideal context for understanding why a CDN link beats local hosting.
Kinsta's guide introduces jQuery as the web's most widely used JavaScript library, covering what it is, what problems it solves, and how it fits into a typical web page. As a thorough overview it is likely to touch on including the library in a project and demonstrate basic usage patterns that the rest of this module builds on.
It puts a concrete face on the abstract idea of a "third-party external library," and it previews jQuery specifically — the first library you will load via CDN in this module.
PowerCert's animated explainer defines a CDN and focuses on its main purpose: making websites load faster by serving content from servers physically closer to the visitor. Expect a visual walkthrough of distributed server locations, caching of static assets, and the performance and reliability benefits that result.
It reinforces the CDN concept with a different visual approach and a slightly slower pace, directly supporting the "Benefits of Using a CDN Over Local File Hosting" subtopic for students who want the idea explained twice.
Together these videos build the conceptual groundwork for MO1: before you can correctly load jQuery, Bootstrap, and Chart.js via script and link tags in the right order, you need to understand what an external library is and why CDN-hosted copies are the standard delivery mechanism. The two CDN explainers cover distribution, caching, and performance so that CDN URLs are not just strings you copy, and the jQuery overview previews the specific library behind MO2's event handling and DOM manipulation work. Understanding versioned CDN links and dependency loading also sets up MO5, where you will reason about combining multiple libraries without conflicts; the hands-on syntax for MO3 and MO4 is developed in the later topics of this module.
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.