The CMS client cannot reach the browser
The content client is marked server-only, so an accidental import from a client component fails the build rather than shipping the API key in the bundle.
03 — Professional services / Legal / 2026
GOODWILLLEGAL
A website for a Sapporo administrative scrivener's office, designed to explain its services clearly and connect consultation enquiries with ongoing content publishing.
2026Sapporo, Hokkaido
- CLIENT
- 行政書士グッドウィル法務事務所
- SECTOR
- Professional services / Legal
- ROLE
- Planning, design, development, CMS, SEO, operations
- YEAR
- 2026
01 / PROJECT
WHAT THE
PROJECT IS.
The project covers the office's service information, consultation flow, profile and access information together with a continuously updated column section.
A CMS was introduced so articles can be published and organised without modifying the site code. The enquiry flow sends consultation details to the office and returns a confirmation to the sender.
I handled the project from site planning and UI/UX through implementation, CMS integration, enquiry functionality, SEO, launch and ongoing maintenance.
02 / HOW IT WORKS
THE DECISIONS
UNDER IT.
FROM THE IMPLEMENTATION
Drafts are blocked twice
The CMS normally returns only published entries, but depending on the key's permissions it can return drafts too. An unpublished article appearing on a legal practice's site is not a cosmetic bug, so the fetch layer filters them out as well rather than trusting the API to have done it.
The site survives the CMS being down
If the content API is unreachable the sitemap is still served from the fixed pages, and with no CMS configured at all the site falls back to fixtures so the build stays green. Pages revalidate on the same interval as the sitemap, so a published article and its sitemap entry appear together.
An enquiry produces two emails
One to the office with the consultation details, one back to the sender confirming it arrived — so nobody is left wondering whether a legal enquiry went through.
03 / DELIVERED
WHAT WAS
BUILT.
- 01
Service and consultation-information pages
- 02
CMS-based article publishing and category structure
- 03
Contact flow with office notification and automatic confirmation
- 04
Office profile and access information
- 05
SEO-oriented metadata, sitemap and content structure
- 06
Ongoing maintenance and content-operation support
04 / TECHNOLOGY
THE STACK
BEHIND IT.
- Next.js
- React
- TypeScript
- microCMS
- Resend
- GSAP