Issue 01
Every update requires development work
Your team cannot update fixed pages or announcements, so even small changes take time.
Site functions / Feature Enhancements
Keep your current site and add only the features you need.
Without assuming a full renewal, we identify bottlenecks in updating, search, inquiries, and publishing and add features using methods that fit the existing architecture.
Starting point / 01
Sustainable operations matter more than adding more features.
Even useful features will not take root if editors cannot use them, they cannot be fixed after launch, or they introduce too many external services. We review the current site, update method, inquiry handling, and publishing flow and design the necessary features and operating rules together.
Issue 02
Required information is hard to find
Articles and pages have increased, but search, categorization, related content, and other journeys are missing.
Issue 03
Context is lost before an inquiry
When visitors move from a service description to the form, the subject they wanted to discuss is not carried over.
Prices are tax-inclusive estimates. External service fees, license fees, server costs, and changes after formal requirements are confirmed separately.
Scope / 02
Features we can add
Choose only the items you need, combined to fit the existing site's architecture and operating structure.
01
CMS and update foundation
We define what should be editable—such as fixed pages, articles, announcements, pricing, and settings—and provide an editing interface.
- Definition of editable content and permissions
- Image-upload and input-field design
- Review and publishing flow using GitHub
CMS Editing Interface From ¥50,000
02
Inquiry AI chat
We build an assistance journey that provides guidance based on site content and routes questions it cannot answer to a formal inquiry.
- Design of answer scope and guidance rules
- Origin checks and rate limits
- Safe link rendering and inquiry journey
Inquiry AI Chat From ¥80,000
03
Comment and posting features
Using Cloudflare Pages Functions, D1, Turnstile, and related services, we establish posting, storage, spam prevention, and deletion operations.
- Posting API and storage design
- Protection against spam and repeated posting
- Operating policy covering approval and deletion
Blog Comment Feature From ¥80,000
04
Article and multilingual publishing foundation
We establish the structures needed for ongoing publishing, including article lists and details, tags, related articles, RSS, and multilingual pages.
- Article model and publishing flow
- Generation of related articles, RSS, and sitemaps
- Translation PR and multilingual URL design
Blog and Article Foundation From ¥50,000
Multilingual Blog Operations From ¥80,000
05
Site search
Using Pagefind or another solution suited to static sites, we add a search journey that makes growing content discoverable.
- Definition of search targets and exclusions
- Search interface and URL parameters
- Build and cache settings
Pagefind Site Search From ¥30,000
06
CTA and form integration
We carry the viewed service, consultation category, and required information into the contact form.
- URL parameter contract
- Initial consultation-category and subject values
- Measurement fields that identify the source journey
CTA and Form Integration From ¥30,000
Process / 03
We review the existing architecture before adding features incrementally.
Decisions consider not only the technology, but also the people who edit, review, and handle the site after publication.
Step 01
Current-state review
We review the site architecture, hosting, update method, and external services in use.
Step 02
Scope design
We define the required features, data involved, permissions, and checks before and after publication.
Step 03
Implementation and review
We implement in reviewable increments and jointly check rendering, input, and error behavior.
Step 04
Publication and handover
We share operating procedures and continue with post-publication fixes and additional improvements as needed.
Technical notes / 04
Technical resources explain the design background.
Acecore Systems technical articles document detailed implementation decisions, while this page defines the scope available for consultation.
Note 01
Technical Design for Inquiry AI Chat on an Astro Site
An overview of API boundaries, answer scope, Origin checks, rate limits, and safe link rendering.
Note 02
Building Astro Blog Comments with Cloudflare Alone
A design record for posting, storage, and operations using Pages Functions, D1, and Turnstile.
Note 03
Sveltia CMS Implementation Guide
An overview of editable content, images, the GitHub backend, and review and publishing flows.
Note 04
Operating a Multilingual Blog with Sveltia CMS
Covers Japanese source drafts, translation PRs, hreflang, RSS, and sitemaps.
Note 05
Multilingual Architecture for an Astro Site
A record of one architecture covering UI translation, article translation, locale-specific URLs, and search information.
Note 06
Astro View Transitions Pitfalls and Solutions
Examples of UX and code-quality improvements for a static site, including Pagefind search.
Note 07
Technical Design for Carrying Service CTA Context into a Contact Form
An implementation contract for passing the consultation category, subject, and source journey into the form.