0008 · Fieldnotes design refinement
English is authoritative; Chinese reference .
Status: local implementation and validation complete on feat/fieldnotes-design-refinement, based on main 184a96b36de71425ee568f902db70c2a9bd67a26, including the footer-motion update. No PR or remote publication.
Reviews: the original refinement selected final independent acceptance, which passed on 2026-09-20; requirements, plan and execution reviews were owner-waived. For the subsequent footer-motion update, the owner waived all four independent reviews. The earlier pass applies only to the refinement before that update.
Requirements
Remove visitor-facing source notes and resume-provenance copy. Refine the existing Fieldnotes identity across Home, Projects, project details and Experience in both languages. Improve visual hierarchy, spacing and consistency while keeping factual content, natural-color photography, project navigation, keyboard access, reduced motion and narrow-screen readability.
Remove the shared footer motion toggle, play the decorative hero route animation once briefly, and continue following the system reduced-motion preference on load and when it changes.
Plan and decisions
- Retain the paper, forest-green and terracotta palette. Use stronger editorial typography, quieter illustration framing and more deliberate section spacing; reuse the existing SVG art and portrait.
- Give the homepage a clearer name lockup and project hierarchy. Refine the project grid, case-study reading layout, experience metrics and shared footer as one composition.
- Remove source-note rendering and obsolete UI strings/styles. Keep provenance fields in authoring metadata for content validation; they are not visitor copy. Preserve meaningful project screenshots and legal attribution.
- Use Astro and existing CSS/native interactions. No dependencies, tool upgrades, route changes or new animation framework.
- Remove the motion toggle’s markup, translations, styles and event handlers. Reuse the existing system-preference listener and CSS overrides; a short, single animation needs no replacement settings UI.
Execution and acceptance
Removed project source-note disclosures, the experience provenance paragraph and their obsolete strings/styles. Authoring metadata and attribution remain available in the repository. Project cards show a single outcome row; role details remain on each case study. The homepage adds the existing Ctrip record count to the work card, larger name typography, section markers and a clearer call to action. Case-study headers, sticky facts, experience metrics, illustrations and the shared contact footer use the same visual system.
Before the final draft-state correction, local pnpm verify passed on 2026-09-20: zero type diagnostics, 22 unit tests, both static builds, 7 output tests, 36 desktop/mobile browser tests and real Markdown build fixtures. The portfolio still produces 17 pages. Additional checks prevent provenance copy in visitor HTML, exercise 320/768px reading layouts and confirm hero labels remain unobscured from 320 to 1440px. Existing checks retain bilingual navigation, keyboard focus, no-JavaScript access, motion controls, local image loading and log-site search.
The acceptance review found that the new Ctrip metadata lookup made Home fail to build when that career pair was drafted. The final implementation guards the Ctrip-specific card, supports a cloud-only or empty highlight stage, and never substitutes another employer under the flight-data headline. The existing real-build fixture now checks drafted career highlights as well as project drafts. After the correction, pnpm check, pnpm build:portfolio, pnpm test:invalid-content, all 7 output tests and 8 relevant browser tests passed (pnpm test:browser --grep 'hero labels|Fieldnotes: featured|narrow and tablet').
Desktop and mobile EN/ZH screenshots were inspected locally. An overlapping hero card was corrected before the successful test run. Screenshots and the detailed Chinese acceptance handbook stay outside public mounts in ignored local storage. No deployment was performed; remote behavior remains unverified.
The footer-motion update removes the control and its unused translations, styling and click handlers. The decorative route animation now ends after one three-second pass; the existing system-preference listener still disables CSS and scripted motion on load and when the preference changes. On 2026-09-21, pnpm check, pnpm build, all 7 output checks and all 36 desktop/mobile browser tests passed. Existing browser checks now cover automatic animation completion, live system-preference changes, reduced motion without JavaScript and the absence of footer buttons across both languages. Four EN/ZH desktop/mobile footer screenshots were inspected locally; no layout issues were found.
Independent acceptance review of the original refinement
On 2026-09-20, before the footer-motion update, the independent reviewer examined the working-tree diff against 184a96b36de71425ee568f902db70c2a9bd67a26: changed portfolio components, layout, UI strings and styles; the content guide; real-build, browser and output tests; this EN/ZH record; and the ignored Chinese acceptance handbook. The scope includes correctness, visual quality, keyboard/motion behavior, factual integrity, first-principles complexity, test/document value, privacy and reproducibility.
Independent checks covered all eight page types in both languages at twelve widths from 320 to 1440px (192 combinations), with no horizontal overflow, key-text clipping, browser errors or residual source-note UI. The reviewer reproduced and verified the draft fix with separate temporary builds and ten cloud-only/no-highlight browser states. The author additionally checked 48 hero motion states. No dependency or new interaction framework was needed; the existing illustration, content-validation and motion mechanisms were reused. Public records contain concise results; detailed steps, screenshots and raw output remain ignored and outside Hugo mounts. Final independent acceptance verdict: PASS, including the corrected draft handling and final record consistency; no unresolved findings. Verification used Chromium and local static builds.
Migration
No migration required. Dependencies, content schema/data, configuration, routes and deployment contracts remain unchanged. This is a presentation change. Recovery after a confirmed commit can use a normal follow-up revert and rebuild; no database, backup or irreversible operation is involved.