Simplify registry contributor workflow

[preetsuthar17]

What changed

• made registry.json the canonical component and block catalog
• replaced copied snippet strings with executable demos, including all 85 blocks
• standardized the repository on pnpm and restored a clean Next.js runtime
• centralized installation commands and added registry validation with Node tests
• moved generated registry and sitemap output out of version control
• added concise contributor documentation and CI

Why

Adding a component or block previously required synchronized edits across several handwritten catalogs, copied code strings, fixture switches, and generated files. Those sources had drifted and were already producing broken installs, missing documentation pages, and localhost compilation errors.

The new workflow requires one registry source, one executable demo, one registry.json entry, and one static demo-map entry.

Validation

• pnpm verify
• pnpm registry:build
• pnpm build
• six registry tests
• required component, block, registry, and OG routes return HTTP 200 on port 3001
• zero tracked public/r/*.json files

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hexta-ui	Ready	Preview, Comment	Jul 15, 2026 10:57am