Content guide

English is authoritative; Chinese reference .

Content locations

Copy the nearest <key>.en.md / <key>.zh.md pair. Keep translationKey and slug identical; translate titles, summaries, body text and display labels. Slugs use lowercase words/numbers and single hyphens. Smaller numeric order appears first; the homepage features the first two projects and lists the remaining projects compactly.

Common fields: lang, translationKey, slug, title, summary, draft and order. Set draft: true to omit an entry from the build. Published entries require both languages; paired entries must agree on slug and draft state. Public Git still exposes draft source: never store private content here.

Projects also require year, category (ai, systems, interfaces), art (cloud, laife, cat, asl, signals), role, period, result, eyebrow and tags. An approved local image is optional. Pick a suitable existing illustration; adding a new visual is a design change. Career entries require organization, period, year, highlights, metric and metricLabel. Report outcomes with their original task and dataset context.

The profile supplies introduction, about.identity, about.paragraphs, shortBio, education and grouped skills, plus the role/school/degree metadata. The Markdown body provides the longer introduction used on Experience. Keep factual changes consistent between these contexts and the translated pair.

Each project/role needs public HTTPS sources, an approved sourceNote, or both. For approved resume content, use a truthful source note without exposing the original filename, path, contact header or PDF. Never substitute an unrelated public URL. Root-level PDF inputs are ignored and must stay outside public/ and Hugo mounts.

Run pnpm verify. New Markdown pairs generate routes without component edits; real-build tests check additions, draft removal, missing translations and invalid slugs.

Engineering records

Follow the workflow : one English article and Chinese reference per change. Hugo reads these records, root contributor documents and docs/ directly. Use relative repository links, record real PR metadata when available, and keep requirements, decisions, selected reviews and verified results in the same article pair.

Temporary Chinese acceptance handbooks belong in ignored .local/acceptance/, outside Hugo mounts. Neither raw sessions nor private evidence belong in public logs or their search index.