https://github.com/mizcausevic-dev/headless-preview-recovery-kit

TypeScript control plane for recovering reliable preview flows, draft routing, and publish validation across headless CMS frontends.
https://github.com/mizcausevic-dev/headless-preview-recovery-kit

content-governance express headless-cms nextjs preview seo typescript wordpress

Last synced: about 1 month ago
JSON representation

TypeScript control plane for recovering reliable preview flows, draft routing, and publish validation across headless CMS frontends.

• Host: GitHub
• URL: https://github.com/mizcausevic-dev/headless-preview-recovery-kit
• Owner: mizcausevic-dev
• Created: 2026-05-17T04:57:25.000Z (about 2 months ago)
• Default Branch: main
• Last Pushed: 2026-05-17T05:13:12.000Z (about 2 months ago)
• Last Synced: 2026-05-17T07:27:19.435Z (about 2 months ago)
• Topics: content-governance, express, headless-cms, nextjs, preview, seo, typescript, wordpress
• Language: TypeScript
• Homepage: https://kineticgain.com/
• Size: 1.49 MB
• Stars: 0
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md

Awesome Lists containing this project

README

          
# Headless Preview Recovery Kit

Headless Preview Recovery Kit is a TypeScript control plane for recovering reliable preview flows, draft routing, and publish validation across headless CMS frontends.

It focuses on the real headless preview problems teams keep tripping over:

- stale draft routes

- broken preview auth

- scheduled pages with missing media or metadata

- editors losing trust because preview and publish do not match

## Routes

- `/` overview dashboard

- `/preview-matrix` draft session recovery lane

- `/recovery-rules` stable rules for restoring preview trust

- `/publish-lane` preview-connected publish readiness

- `/verification` proof posture

- `/docs` route and payload reference

## What this repo proves

- headless preview reliability is a platform problem, not only an editorial problem

- route, auth, cache, and media drift all need to be governed together

- preview health should be treated as publish readiness infrastructure

- one healthy preview pattern is worth more than many one-off fixes

## Screenshots

![Overview](./screenshots/01-overview-proof.png)

![Preview matrix](./screenshots/02-preview-matrix-proof.png)

![Recovery rules](./screenshots/03-recovery-rules-proof.png)

![Verification](./screenshots/04-verification-proof.png)

## Local development

```powershell

cd headless-preview-recovery-kit

npm install

npm run dev

```

## Validation

- `npm run build`

- `npm run test`

- `npm run demo`

- `npm run smoke`

- `npm run render:assets`