Advanced

A longer page used to verify Atlas’s right-rail “On this page” rendering with multiple H2/H3 levels.

Async patterns

When ingesting customer commits, the build pipeline serializes per-tenant work to keep the change-detection cache coherent.

Webhook-triggered builds

The git-backed:reindex-on-push job runs in the tenant’s job scheduler. Failures on one backing don’t prevent the others from reindexing.

Polling fallbacks

If the webhook never lands (delivery failure, worker queue stalled), the rebuild indicator’s drift check pays one cheap GitHub HEAD call per change-detection request and self-heals.

Auth patterns

Out of scope for site.json v1. The plan calls for adding auth.jwt later; for now JWT config stays in the Jolli UI’s read-only status page.

What customers configure today

Nothing — the keypair is Jolli-managed. Visitors hit /api/sites/:id/auth/jwt to obtain a token; the deployed Nextra middleware verifies via JWT_PUBLIC_KEY.

What customers will configure later

auth.jwt.{enabled, mode, allowedGroups, showAuthBanner, crossTenantAccess} in site.json. Keys never leave Jolli.

Notes

This page exists mainly to give Atlas’s TOC component something to render. Three H2 sections, two H3 subsections per H2.