Dr Frankenstein of Grndwerk
Hey PH 👋 Werner here, Dr Frankenstein of Grndwerk.
Every Next.js project I shipped for clients started the same way... two days of wiring schemas, metadata, and llms.txt before writing a single line of actual product. The fourth time it happened, I stopped and built this instead.
The idea is simple: one constants.ts file. You fill in your business name, URL, and a few details. Schemas, metadata, llms.txt, and sitemap all derive from it automagically. Change one value: everything updates. BAM!
A few things I'm proud of that you won't find elsewhere:
owned-asset mode - suppresses Person schemas for rank-and-rent/agency handoff sites
Debug dashboard at /debug - shows schema health, validation warnings, and a live llms.txt preview before you deploy                                Â
16 page archetypes - home, serviceDetail, article, product, location, and 11 more, each wiring the correct schema types automatically
Happy to answer anything. How it works under the hood, how to adapt it for your stack, and whether it fits your use case. Ask away.
Replies