PawScapes is a dog-friendly travel directory for Australia, written in the voices of two dogs, Pepsi and Max. Most of it is machine-built: a census and enrichment pipeline finds venues, verifies pet policies, mirrors photos and drafts guides into a 62-column venues table in Cloudflare D1. People polish what the pipeline makes, and write the parts it can't: the diary, guides, trip plans and news.

That split is why highseam exists. The CMS that became highseam started inside the PawScapes admin repo as svelte-payload, and moved to the public npm package [email protected] on 6 August 2026. Since then PawScapes has tracked highseam releases closely, usually adopting them the day they ship.

How it's put together

  • Two deploys, one database. The admin (PawScapes Studio) and the public site are separate Cloudflare Pages projects sharing the pawscapes-db D1 database and the media bucket.
  • The public site doesn't run the CMS. It reads D1 with its own SQL and imports five small highseam modules: preview-token checks, the preview banner, rich-text types, media helpers and link resolution.
  • Two storage modes side by side. venues and contact_messages are table-backed collections over tables the pipeline and site already owned. Editorial content (diary, guides, trip plans, news, pages, destinations, regions) lives in JSON-document collections.

What the articles cover

Each article takes one highseam feature and shows how PawScapes uses it, including the parts that didn't work the first time.