Project
LifeExchange Multilingual Knowledge Archive
An evidence-aware Chinese, English, and German site for essays, projects, Zhihu QA, tags, search, and a downloadable portfolio.
Astro · TypeScript · Pagefind · Supabase · Vercel
Product Snapshot
- Role
- Independent product design and engineering
- Users
- Readers, collaborators, and recruiters who need a fast but verifiable view of my work.
- Stage
- Continuously deployed and maintained in production.
- Focus
- Multilingual content modeling, QA archival, project evidence, static search, information architecture, and deployment quality.
- Validation
- Shipped Chinese, English, and German essays and projects, a Zhihu QA module, tags, Pagefind search, RSS, and a downloadable portfolio.
- Public Proof
- Source, content-model checks, static builds, search indexes, and Vercel production deployments are reproducible.
Next Step
More than a chronological blog
The site must serve first-time visitors, evidence-sensitive readers, and my future maintenance workflow. I designed it as a knowledge archive rather than an endless reverse-chronological feed.
Content system
A shared schema manages essays, projects, and QA across Chinese, English, and German source-translation relationships. Project cards separate role, stage, result, proof, and stack so that a marketing sentence cannot hide the actual boundary.
Zhihu answers become structured QA entries with source, date, tags, and backlinks. Archives, RSS, tags, and Pagefind make older material discoverable without homepage exposure.
Engineering delivery
Astro generates static pages, TypeScript constrains content and routing, Pagefind builds a local full-text index, and Vercel hosts production. Content checks block duplicate entry IDs, missing translation links, and inconsistent metadata.
The site also publishes a downloadable PDF portfolio and separates the public blog from a more private workspace workflow.
Evidence-aware writing
This Mac-wide project audit became a stress test for the model. Every new case must state who did the work, what stage it reached, where a number came from, and what cannot be public.
Ongoing state
The site is live, but the archive continues to evolve. Repeatable checks, builds, indexing, and deployment are what make that evolution maintainable.
Configure the public Giscus environment variables to open discussion on the public site.