Challenge
Keep the publishing foundation simple.
As content and features increased, the architecture still needed to guide visitors to the right information and isolate the impact of updates and incidents.
Case Study / Site Foundation
Turning a static site into an operable foundation.
An internal project that progressively added a CMS, search, SEO, and delivery quality while preserving the light weight of a static site.
Overview / 01
A site foundation that can keep evolving.
On a foundation of Astro and Cloudflare Pages, we added a CMS, search, and other features in independently verifiable increments. Editing, review, and publishing are organized as one operating workflow.
- Target
- Acecore corporate site
- Publishing foundation
- Astro / Cloudflare Pages
- Update workflow
- Sveltia CMS / GitHub
- Position
- Internal project
Current state
What the project enabled
Updates
Fixed pages, articles, and settings can be updated through the CMS
Information discovery
Visitors can reach the information they need through search and internal journeys
Publishing quality
SEO, CSP, accessibility, and display quality can be reviewed in the same publishing flow
Challenge and approach / 02
Keep it simple and ready to evolve.
Approach
Design features and the publishing flow together.
We separated the CMS, articles, search, and other features by role, and treated who edits, where changes are reviewed, and how they are published as part of each feature.
Implemented scope / 03
Scope improved in stages
Rather than adding each item in isolation, we considered its connection to publishing, review, and operations.
01
Updates and article operations
We created a browser-based editing entry point and a flow for reviewing changes through GitHub.
- Editing fixed pages, articles, and settings with Sveltia CMS
- Organized image-upload destinations and input fields
- Article lists, tags, related articles, and RSS
02
Information discovery and internal journeys
We added a structure that helps visitors reach the information they need through search and related links even as the number of pages grows.
- Site search with Pagefind
- Defined search targets and exclusions
- Internal links among services, pricing, and articles
03
Information for search engines
We aligned page roles and URLs and made the information needed in search results and social sharing consistent.
- title, description, OGP, and canonical
- JSON-LD including Organization, WebSite, and WebPage
- Alignment of sitemap and multilingual URLs
04
Publishing quality
We reviewed safety, usability, and display speed together with the delivery architecture instead of adding them separately afterward.
- CSP, security headers, and caching
- Keyboard operation, focus, and forms
- Images, CSS, fonts, and external scripts
Related support / 04
Services used in this case
Technical notes / 05
Technical resources explain the decisions in detail.
Acecore Systems technical articles document our architecture and implementation decisions.
Note 01
CMS and publishing flow
A design record covering editable content, images, the GitHub backend, review, and publishing.
Note 02
Search and internal journeys
Examples of UX and code-quality improvements, including Pagefind search.
Note 03
Delivery quality and security
An overview of CSP, security headers, caching, and Pages delivery settings.