The Nahkur CMS loop underneath the craft site.
A one-man workshop cannot treat every catalogue edit, price change or portfolio update as a developer ticket. The public site still needed to stay static, fast and hard to break.
How these were measured: Source: clients/nahkur/TECH.md records the shipped CMS loop, 4 render passes, bilingual catalogue data, and live verification. The visual proof is public/showcase/nahkur-tall.webp.
What we shipped
kratt put a CMS-backed render loop under Nahkur: catalogue data, Valencia product data, portfolio cards and hourly-rate copy are all rendered from editable data. The story belongs here because the deliverable is the editor-to-production path, not a regular website showcase.
What this page does not claim
- No traffic, ranking, inquiry or revenue claim. The client record explicitly says the site has no analytics, so this page does not pretend otherwise.
- No private payment-status detail is published here.
- No CMS secret, token, deploy hook or account detail is exposed.
Where is your business leaking revenue?
A free AI audit finds it, ranked by impact, and it is yours to keep.
Back to all case studies, or see every live build on the portfolio wall.