doxa-life/doxa-maps

Fork 0

History

Doxa Maps 85a4172644 Some checks are pending Deploy to GitHub Pages / build (push) Waiting to run Details Deploy to GitHub Pages / deploy (push) Blocked by required conditions Details Merge APPROXPIN and rebuild against the library it moved studio's APPROXPIN (`dee9f9c9`) moved library/ — legends, PinHint, useMapInstance, i18n — so the rebuild was certain rather than conditional this time. Checked, as always, with `git diff --name-only <base> <main> \| grep '^library/'` rather than assumed: that test was EMPTY on one earlier merge and NON-EMPTY on the next two, and it is the only thing that decides whether the bundle must follow. All conflicts were DERIVED artifacts again — my two leaf HTMLs and the manifests, zero source conflicts. Resolved to main's fresh build, then regenerated from the merged source, because picking a side of a generated file is meaningless. VERIFIED BY HASHING, the step whose absence shipped a blank page: fix:sri rewrote the two manifests, and I then recomputed sha384 over the actual bundle — upg-100-list, upg-100-mfe and poster-wall all MATCH, whole-tree sweep 57 integrity attributes with 0 mismatches. fix:sri, not tree: studio had already regenerated the pages and the gate itself warns that tree re-reads .vue source on a shared branch.	2026-09-26 13:20:45 +00:00
..
dx-maps	Merge APPROXPIN and rebuild against the library it moved	2026-09-26 13:20:45 +00:00
README.md	Rename the output folder to dx-maps	2026-09-25 19:26:14 +00:00

Doxa Maps 85a4172644

Deploy to GitHub Pages / build (push) Waiting to run

Details

Deploy to GitHub Pages / deploy (push) Blocked by required conditions

Details

Merge APPROXPIN and rebuild against the library it moved

studio's APPROXPIN (dee9f9c9) moved library/ — legends, PinHint, useMapInstance,
i18n — so the rebuild was certain rather than conditional this time. Checked, as
always, with `git diff --name-only <base> <main> | grep '^library/'` rather than
assumed: that test was EMPTY on one earlier merge and NON-EMPTY on the next two,
and it is the only thing that decides whether the bundle must follow.

All conflicts were DERIVED artifacts again — my two leaf HTMLs and the manifests,
zero source conflicts. Resolved to main's fresh build, then regenerated from the
merged source, because picking a side of a generated file is meaningless.

VERIFIED BY HASHING, the step whose absence shipped a blank page: fix:sri rewrote
the two manifests, and I then recomputed sha384 over the actual bundle —
upg-100-list, upg-100-mfe and poster-wall all MATCH, whole-tree sweep 57 integrity
attributes with 0 mismatches. fix:sri, not tree: studio had already regenerated the
pages and the gate itself warns that tree re-reads .vue source on a shared branch.

2026-09-26 13:20:45 +00:00

dx-maps Merge APPROXPIN and rebuild against the library it moved 2026-09-26 13:20:45 +00:00

README.md Rename the output folder to dx-maps 2026-09-25 19:26:14 +00:00

README.md

public/ — the built output

This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:

dx-maps/ — the output folder: 23 plugin bundles and 35 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.
- dx-maps/index.html — the front page: the Plugin Studio, every plugin in one place.
- dx-maps/<plugin>/<plugin>.js — a plugin's bundle (a custom element; load it with a <script> tag).
- dx-maps/<plugin>/<page>/index.html — a ready-made page for one plugin view (embed it in an <iframe>).
- dx-maps/manifest.json — every plugin, page and embed snippet, machine-readable.
- dx-maps/assets/ — the data, fonts and images the plugins fetch at runtime.

The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.