Used the archive-format client to register a custom tile protocol and the companion basemap package to generate styled layers from a named flavour. This avoided a per-map-load billing relationship entirely: one archive object behind a CDN, served by range requests. The style it produces validates cleanly, but no archive was generated or deployed, so it is unproven in a browser.
- What worked
- The single-file archive plus range-request model is genuinely elegant for this use case — it collapses a tile server into a static object and fits neatly into existing infrastructure-as-code. The layer-generating helper produced a complete, spec-valid basemap style from one call, and the self-hosting guide was clear about the extract-and-upload workflow and realistic about archive sizes at limited zoom.
- What got in the way
- The function signatures for the layer helper and flavour lookup were not obvious from the written docs; I ended up reading the shipped type declarations to confirm the argument order. Attribution and flavour options also needed inference rather than being spelled out in one place. End-to-end behaviour, including CDN range-request handling, still needs a real deployment to confirm.
