Duc-Tam Nguyen
3af26ae0e5
Rework the README into the house style: badges, a one-line pitch, an anchor nav, a commands table, and dedicated sections for clone, pack, and the native viewer. Every flag and default is checked against the current binary so the docs match what kage actually does. Add a demo recorded with ascii-gif. The tape clones example.com, packs it to a ZIM and to a self-contained binary, and serves it back offline, so the whole loop reads in one frame. It sits at the top of the README and on the docs home. While reviewing the docs, fix the output path everywhere: the default is $HOME/data/kage, not the kage-out the pages claimed, including a few fabricated 'done kage-out/...' lines. Document pack, open, and the native viewer in the release notes.
2.4 KiB
2.4 KiB
title, description, heroTitle, heroLead, heroPrimaryURL, heroPrimaryText
| title | description | heroTitle | heroLead | heroPrimaryURL | heroPrimaryText |
|---|---|---|---|---|---|
| kage | kage (影, shadow) clones any website into a self-contained folder you can browse offline, with all the JavaScript stripped out. Render in headless Chrome, remove every script, localise the CSS, images, and fonts, from one pure-Go binary. | A website, frozen as a shadow | kage renders every page in headless Chrome, snapshots the final DOM, removes every script and event handler, and downloads and rewrites the CSS, images, and fonts. The result looks like the live site but runs no code: a plain folder of .html files you can open straight from disk. | /getting-started/quick-start/ | Get started |
Saving a page with "Save As" gives you a copy that still phones home, still runs analytics, and often renders blank because the markup is built by JavaScript at runtime. kage (影, "shadow") takes the opposite approach: it drives a real browser, captures the page the way a human would have seen it, then makes it inert.
kage clone example.com
kage serve $HOME/data/kage/example.com
What it does
- Renders first, saves second. Each page goes through real headless Chrome, so a page whose content is assembled by JavaScript is captured fully, not as an empty shell.
- Strips every script. Once the DOM is captured, kage removes all
<script>tags, everyon*event handler, and anyjavascript:URL. The saved page makes no network calls and runs no code. - Keeps the layout. Stylesheets, images, fonts, and media are downloaded and rewritten to relative local paths, so the offline copy looks like the original.
- Stays browsable. In-scope links are rewritten to point at the other saved pages, so you can click around the mirror exactly as you would the live site.
Where to go next
- New here? Start with the introduction, then the quick start.
- Want to install it? See installation.
- Looking for a specific task? The guides cover scoping a crawl, serving a mirror, resuming an interrupted run, and packing a mirror into one file or a self-contained viewer.
- Need every flag? The CLI reference is the full surface.