Objective
Build the extension for production, write real store/install assets, and either submit to the Chrome Web Store or package for side-loading.
Build
The capstone project
All 4 features work. Today's job isn't code — it's the difference between "runs on my machine in developer mode" and "a real person who isn't you can install this and it works."
Two real paths, pick one honestly
Chrome Web Store costs $5 once and takes real review time -- know this before you start this lesson
Publishing requires a one-time $5 developer registration fee and a review process that can take anywhere from a few hours to several days. This isn't a blocker, but it's real information to have before committing to this path over side-loading, especially if your goal this weekend is "I want this live today."
Path A — Chrome Web Store: real discoverability, a real listing, but requires the fee, a privacy policy (required if you handle any user data, which an API-key-storing extension does), and passing review. Path B — side-loading: package the built extension as a zip, write clear installation instructions (load unpacked, or drag the .crx), share via GitHub — free, instant, but the person installing it has to trust a direct file rather than a store listing.
### Installing Page Intelligence (unpacked)
1. Download and unzip `page-intelligence.zip` from this repo's releases
2. Open `chrome://extensions`
3. Enable "Developer mode" (top right toggle)
4. Click "Load unpacked" and select the unzipped folder
5. Click the extension icon, open Settings, and add your own Anthropic API key
Notice step 5: EVERY installer needs their own API key, because (Lesson 2's warning, still true) you never ship a hardcoded key. This is the actual reason "the settings pattern" from Lesson 2 matters beyond just this course's build — it's what makes the extension shareable at all without you paying for every installer's usage.
Chrome Web Store requires a privacy policy the moment you handle ANY user data
Storing an API key in chrome.storage.local counts as handling user data for Web Store purposes, even though it never leaves the user's machine. A short, honest privacy policy ("this extension stores your API key locally in your browser; it is never transmitted anywhere except directly to Anthropic's API using your own credentials") is a real, required submission field, not optional legal boilerplate you can skip.
You're deciding between Chrome Web Store submission and side-loading for your extension's first release. Your goal is "have something live and shareable by tonight." Which path fits, and why?
This isn't about which path is "better" in the abstract -- it's about matching the path to the actual constraint (same-day shipping). Web Store review timing isn't fully in your control; side-loading is. Nothing stops you from side-loading tonight and submitting to the Web Store later once you've used it for a while and are confident in it — the two paths aren't mutually exclusive across time, just for a same-day deadline specifically.
Ship it
Package your extension (zip for side-loading, or submit to the Web Store if you've chosen that path). Navigate to a real page you actually care about, click Summarize, watch it work in under 5 seconds. Record it.
Ship Prompt: Share a screen recording of it working on a page you actually care about. What's the URL? What did it do? If you submitted to the Web Store, drop the link.