Generated output — do not hand-edit. The rendered build site, produced by `scripts/build_html.py` from the markdown in `../` and `../weapons/`. This is the deploy artifact for https://d2builds.pages.dev (Cloudflare Pages).
The markdown builds are the source of truth. Any edit made directly to a `.html` file here is lost the next time the site is rebuilt.
`data/owned.json` — per-card Owned / Not-owned marker + a "Your vault" filter + the "N of M runnable now" index summary.
`data/gear_stats.json` — per-card gear-readiness chip, a per-page "Your gear" ceiling box, and a Gear-ready filter.
All three degrade cleanly — without them you get a clean, un-personalised site.
Contents
`index.html` — the landing page: every build as a filterable card grid (category + element + weapon-type + artifact filters, plus the owned/gear filters when the json files are present).
`hunter_*.html` — one page per exotic-armour build (47).
`weapon_*.html` — one page per exotic-weapon build (140).
`armor_audit.html` — the vault cleaner view (only when `data/armor_audit.json` exists, from `clean_armor.py`): every Hunter armour piece as a keep/junk/review card, filterable by verdict and slot. Linked from the index header. - Read-only by default — the actual lock/unlock and dismantle happen via the CLI / in-game. - Optional live actions: if `data/web_oauth.json` exists (a public Bungie OAuth client_id + api_key — see `data/web_oauth.example.json`), the page grows a "Live actions" panel: sign in with your own Bungie account (token kept in the tab's sessionStorage only) and run the reversible writes — lock keepers, unlock junk, empty postmaster — straight from the page on the baked instance IDs. Still never dismantles (the API can't).
~196 files in total (195 builds + the index), all self-contained (inline CSS, inlined item icons, OG tags + favicon).
Deploy
Push the contents of this folder to Cloudflare Pages (the `d2builds` project) — the same manual flow as the workspace's other `*.pages.dev` sites. Rebuild first so the HTML reflects the current markdown and personalisation json.
The public deploy bakes in the owner's gamertag + which exotics they lack. Fine for a personal site; gate it behind a flag before any clean public release.