HistorySyncWeb.
The product website and download distribution system for HistorySync, combining an Astro marketing site with a Cloudflare Worker release API.
A desktop app still needs trustworthy release infrastructure and a product story.
HistorySyncWeb supports the public-facing side of HistorySync: the multilingual product site, release catalog, download routing, and updater-facing metadata APIs.
The project turns the website and download service into shared infrastructure instead of manually maintained marketing pages.
A static site and edge API consume one canonical release package.
- W1Astro main site
The product site uses Astro static generation, Tailwind CSS, localized copy dictionaries, SEO routes, and a dashboard-style demo surface.
- W2Cloudflare Worker API
The download API handles release metadata, localized changelogs, batch lookup, and platform-aware direct download redirects.
- W3Shared release catalog
A TypeScript package stores canonical release data so the site and API do not drift apart.
The release path is built around consistency, localization, and low operational weight.
Most product pages can be deployed as fast static assets while preserving multilingual routes.
One shared package prevents the marketing site and download API from reporting different versions.
The Worker can choose platform assets, recommend mirrors, and localize responses close to the request.
The result is a small but real distribution layer for a desktop product.
Localized site
Ten static language dictionaries cover English, Simplified Chinese, Traditional Chinese, Japanese, Korean, German, French, Spanish, Russian, and Italian.
Updater API
Desktop clients can query stable and beta release metadata, asset URLs, hashes, sizes, and changelog entries.
Changelog taxonomy
Release notes are grouped into feature, fix, improvement, performance, security, breaking, docs, deprecated, and internal categories.
Cloudflare deployment
Cloudflare Pages and Workers keep hosting, routing, observability, and API deployment lightweight.