Build on the index

Data plane & public JSON

ALASKA.FYI is static-first: HTML from Eleventy, JSON alongside the build, and an optional GitHub JSON workspace for larger or collaborative datasets.

On this site

• /topics/ — boroughs, parks, trails, coast (agency handoffs)
• /data/alerts.json — alerts feed (see alaskafyi-web/src/data/alerts.schema.json in the repo)
• /data/gazetteer/*.json — gazetteer exports for lakes, mountains, towns, and more
• /json/index.json — catalog mirrored from the monorepo alaskafyi-json/public tree

alaskafyi-json (GitHub)

Versioned, open JSON and schemas can live in the alaskafyi-json repository for mirrors, PRs, and reuse outside the site build.

Partner “Start here” badges

Reciprocal assets for AFCA, TrueTopo, and AlaskaIntel footers — link to the matching hub on this index. Files are static SVG under /brand/badges/.

• /brand/badges/start-here.svg — generic index
• start-here-fishing.svg → link to /fishing/
• start-here-maps.svg → /maps/
• start-here-intel.svg → /intel/

Example (fish routing):
<a href="https://alaska.fyi/fishing/" rel="noopener" target="_blank"><img src="https://alaska.fyi/brand/badges/start-here-fishing.svg" alt="Start at ALASKA.FYI — fish hub" width="220" height="44" loading="lazy" /></a>

Quality gates (repo)

npm run validate:data · npm run validate:links (after build) · npm run validate:outbound (agency + partner URLs) · CI Lighthouse on key URLs

Changelog cadence

Ship a short quarterly note (homepage editorial strip, this page, or report/) when feeds, hubs, or partner handoffs change — enough for freshness without a blog.