Challenge: Visitors had difficulty knowing what they could discuss, and inquiry details were easily fragmented.
Proposal: We combined service-specific journeys, inquiry categories, FAQs, and AI guidance to collect the necessary information in the form.
Outcome: Separating pre-consultation guidance from formal inquiries made it easier to proceed to an estimate or service discussion.

Challenge: Merchandise sales needed to keep inventory risk low while clearly presenting prices, shipping, returns, and seller information, and reliably connecting payment with manufacturing and delivery.
Proposal: Using Astro and Cloudflare Pages / Pages Functions, we combined D1, R2, Queues, Turnstile, Stripe Checkout, and the Printful API. Customers can confirm shipping and their total from the cart, then proceed from payment completion to manufacturing and delivery.
Outcome: We launched a sales foundation where customers can browse goods by Acecore and Aceserver brand and each order is sent for on-demand manufacturing. Payment information is not retained by the store, making it safer and easier to operate.

Challenge: The architecture needed to strengthen publishing and inquiry journeys without sacrificing the speed or operability of the static site.
Proposal: We combined Astro, Cloudflare Pages, Sveltia CMS, Pagefind, structured data, and security headers in a structure where required features can be added incrementally.
Outcome: The resulting foundation allows blogs, fixed pages, search, and inquiry journeys to be operated and improved, and produced reusable knowledge for similar site-enhancement projects.

Challenge: As participation grows, connection stability, information sharing, incident response, and operational rules require more structure.
Proposal: Instead of separating technical and community operations, we improved the server architecture, monitoring, backups, and Web journeys together.
Outcome: Knowledge from long-term operations can now inform monitoring and operational design for business systems.

Challenge: Information about the server, how to join, rules, videos, and world maps was spread across multiple locations, making the first step unclear for new visitors.
Proposal: Without replacing existing information sources, we built a portal that guides visitors from the server introduction to Discord, videos, each world map, and the Wiki.
Outcome: It is published as a static site using Astro, UnoCSS, and Sveltia CMS. Page content and site settings can be updated through the CMS.

Challenge: The new structure needed to preserve the existing site and blog content while helping visitors proceed to courses and trial lessons and allowing updates to continue.
Proposal: We combined Astro, UnoCSS, Sveltia CMS, and Pagefind into one operating foundation covering existing-article migration, legacy URL redirects, site search, and CMS updates.
Outcome: Visitors can more easily find school information, trial lessons, daily announcements, and older articles, while CMS changes can be reviewed in a PR before publication.

Challenge: Entry points were split among a blog, external publishing sites, BOOTH, YouTube, X, and other services, making it hard for first-time visitors to understand the full scope or viewing order.
Proposal: We organized the work into 3 areas—illustration, novels, and modeling—and built a hub linking the blog, works, profile, and external services.
Outcome: It is published as a static site using Astro, TypeScript, UnoCSS, Sveltia CMS, and Pagefind. Blogs and work information can be updated through the CMS, and articles and works are searchable.

Our work and its outcomes.

Case studies