The public interface prioritizes service clarity and direct contact.
Overview
Problem
The company relied mainly on word of mouth and had no effective online presence. The goal was to clarify services, improve local discoverability and make contact immediate.
Constraints
Zero technical knowledge on the client side — content updates must be autonomous
Minimal budget — no room for custom backends or paid CMS platforms
Fast time-to-market — the site needed to be live within weeks, not months
Solution
A fast marketing website with clear service page sections, structured content and a low-friction path from search to contact.
Impact
Automated
Deployment
Client-managed
Content management
Static-first
Architecture
Key decisions
Why Astro?
The project prioritized performance, SEO and low maintenance over complex client-side interactions.
Trade-off: Less ecosystem maturity than Next.js, but the zero-JS-by-default model fits a content-heavy marketing site.
Why Decap CMS + Git Gateway?
The client needed editorial autonomy without introducing the complexity or cost of a traditional backend.
Trade-off: Git-based publishing is less familiar than a traditional CMS, but avoids hosting costs and vendor lock-in.
Why Netlify Identity?
Netlify Identity provided a simple authentication layer for the admin flow and integrated with the Git-based publishing pipeline.
Trade-off: It ties the project to Netlify, but simplifies deployment and fits the client's needs.
Implementation
The implementation focused on three areas:
Building reusable page sections
Optimizing the information hierarchy
Integrating a Git-based CMS that allows the client to publish content independently.
Workflow
Content publishing workflow
The workflow reduces developer involvement in routine content edits.
01
Admin edit
The client updates text through the admin interface
→ No developer dependency for routine changes
02
Decap CMS save
The content change is saved through the CMS workflow
→ Version-controlled content with rollback capability
03
GitHub update
The change is committed to the repository
→ Full audit trail of every content change
04
Automatic deploy
A new production build is triggered automatically
→ Changes go live in under 60 seconds
Selected views
The admin area lets the client update content without developer edits.
Lessons learned
Structured content reduces maintenance cost and makes the site easier to extend
Git-based CMS workflows need clear onboarding for non-technical clients
Early SEO setup compounds quickly for local businesses
Next steps
Core architecture is ready for production. Remaining work: final content validation, launch preparation and post-launch monitoring.
