KRW Renovasi Website CMS

Key Features

• 01Publish project entries through a custom CMS workflow
• 02Generate 11 local landing pages from structured content data
• 03Expose 7 dedicated service pages for high-intent search terms
• 04Upload media directly to S3 with presigned URLs
• 05Route contact leads to Discord in seconds
• 06Render project pages with static SEO metadata and JSON-LD

Project Details

KRW Renovasi is a conversion-focused contractor website and lightweight CMS built to publish 25 public pages from a single codebase. We designed it for an Indonesian renovation company that needed 7 service landing pages, 11 location SEO pages, and project portfolios in one fast experience. The public site answers high-intent searches for renovation and contractor keywords, while the admin area lets the team publish projects without editing source files. The result is a marketing stack that combines lead capture, media management, and static SEO coverage in one Next.js 16 deployment. We built the system as a single-developer engagement with direct stakeholder feedback and a tight operational scope. The public layer covers 5 core marketing pages, 7 service pages, 11 local landers, and 2 portfolio detail pages, while the CMS exposes project create, update, publish, and media workflows. Contact submissions post into a Discord webhook so leads arrive in seconds instead of sitting in email. That structure gave the client one operational hub for content, media, and inquiries without adding a third-party CMS license. We implemented the stack with Next.js 16.2.2 App Router, React 19, TypeScript 5, Tailwind CSS 4, Prisma 7.6, PostgreSQL, and presigned Amazon S3 uploads. Public pages use generateStaticParams for the 18 evergreen SEO routes, route-level metadata, JSON-LD, robots, and a dynamic sitemap. We kept the data model intentionally small at 4 Prisma models—Project, ProjectImage, ProjectTag, and MediaFile—because the content shape is narrow and the admin flow depends on predictable revalidation. The most important engineering decision was separating static marketing reads from admin mutations so the site stays crawlable and fast. The delivered product expanded service coverage from 1 generic layanan section to 7 dedicated service pages and from 0 local landing pages to 11 geo-targeted routes. It ships 25 public pages and 30 total app routes in production, with standalone output for simpler deployment. The CMS reduces publishing work to one form-based flow, supports direct S3 media uploads, and revalidates homepage, portfolio, and detail pages after every change. For a small contractor brand, that means faster content iteration, better long-tail search coverage, and a site that is ready to scale beyond the first 2 published projects.