ChromeArchivalPlugin Overview
ChromeArchivalPlugin (packaged in the popup as APTlantis Archival) is a Chrome MV3 extension that turns "I want to keep this page" into a deterministic set of local archival artifacts: page metadata, cleaned article markdown, full-page markdown, screenshots, paginated PDFs, and harvested link lists — all written under a predictable APTlantis/ folder in your downloads.
Who it's for
An operator doing manual web archival/ingestion — saving pages for later processing by other Aptlantis tools rather than relying on a browser's bookmark list or an external "save page" service.
The core concept
Everything runs from a single popup UI, with each action producing a specific file type into a deterministic subfolder:
| Action | Output | How |
|---|---|---|
| Add Page | Title + URL + timestamp → browser local storage | chrome.storage |
| Capture Links on Page | Harvests HTTP/HTTPS links into the saved list | DOM scan |
| Export List | One URL per line, plain text | chrome.downloads |
| Metadata capture | Open Graph + JSON-LD → JSON | DOM parsing |
| Article capture | Clean article markdown | Readability.js + Turndown (vendored) |
| Full-page markdown | Full document body → markdown, absolute links/images | Turndown |
| Screenshots | Viewport or full-page PNG | chrome.tabs / DevTools |
| PDF export | Paginated PDF | chrome.debugger → DevTools Page.printToPDF |
Chrome system pages (chrome://, edge://, about:, chrome-error://, view-source:) are intentionally rejected by the screenshot/PDF capture paths — there's nothing meaningful to capture there, and the extension explicitly refuses rather than producing a broken artifact.
Why this shape
Using chrome.debugger's Page.printToPDF (rather than the browser's native print dialog) is the notable technical choice here — it's what makes unattended, paginated PDF export from a popup click possible at all. Vendoring Readability.js and Turndown rather than depending on a build step keeps the extension a plain unpacked directory that loads with zero build tooling — appropriate for a single-operator utility that's reloaded via chrome://extensions rather than distributed through the Chrome Web Store.