New to Hypermake?

Get started in minutes

Hypermake and LZR templating help you build content systems that are addressable, incremental, and inspectable. Run the standalone corpus locally, then open the Inspector to follow source, data, graph, and rendered output.

Run the corpus shell

cd path/to/hypermake/fixtures/lzr-testing
hypermake serve public --inspect --addr 127.0.0.1:8080 --origin https://lzr-testing.localhost

Incremental by default

Only rebuild what changed. Repeat public builds should settle to no-op.

hypermake public --summary

Addressable content

Every source, data, and rendered output has a stable protocol-style address.

src://index.html

Inspectable system

Browse the graph, data, and rendered outputs in the Inspector.

/_hypermake/inspector/

How it works

One graph. Three representations. Every major surface is addressable and can be explained by Hypermake.

Source

<set key="campaign"
     value="{{ data://campaign.json }}" />

<h1 id="campaign-title">
  {{ campaign.client }} Campaign
</h1>

src://components/component-bound.html

Data

{
  "title": "Corpus Campaign",
  "client": "Corpus Client",
  "adCount": 2,
  "assets": [ ... ]
}

data://campaign.json

Rendered

<h1 id="campaign-title">
  Corpus Client Campaign
</h1>

rendered://public/components/component-bound.html

Addressable. Composable. Inspectable.

Graph health

Check graph health shell

hypermake doctor
hypermake public --summary
hypermake explain public://_hypermake/testing/latest.json
hypermake explain public://_hypermake/testing/readiness.json

Core addresses

source src://index.html data data://testing-scenarios.json testing public://_hypermake/testing/latest.json readiness public://_hypermake/testing/readiness.json rendered rendered://public/testing.html

Local dev routing

Readiness checks

Check	Command	Expected
Graph health	`hypermake doctor`	status ready
Cold or stale build	`hypermake public --summary`	build succeeds and reports the current stale set
Repeat no-op build	`hypermake public --summary`	built=0 after the graph has settled
Testing digest artifact	`hypermake explain public://_hypermake/testing/latest.json`	fresh.proof_verified
Readiness artifact	`hypermake explain public://_hypermake/testing/readiness.json`	fresh.proof_verified
Inspector session route	`curl -sk https://lzr-testing.localhost/_hypermake/inspector/api/session`	JSON response from the active hypermake serve process
WebExtension tabs	`open DevTools Hypermake panel on https://lzr-testing.localhost/testing.html`	Timeline, Source, Data, Testing, and Diagnostics hydrate without 4xx/5xx errors