Private Pro template · implemented
Field Notes Portfolio
A designer-developer portfolio with case studies, writing, experiments, and availability. The public page exposes only reviewed source-free metadata; private React, TypeScript, tests, and release files never enter this application.
Product route contract
//work/work/[slug]/notes/about
State and quality contract
States: loading, empty, error, success, permission-denied, offline.
Requirements: responsive, light, dark, rtl-reviewed, keyboard-reviewed, seo-ready.
Evaluate the product fit
Field Notes Portfolio suits an individual designer-developer who needs case studies, short writing, experiments, and current availability to form one credible body of work. It separates finished project evidence from exploratory notes so readers can understand what was delivered, learned, or merely tested.
Review case-study authorship, client permission, contribution boundaries, dates, and links before publication. Notes need a durable archive and clear status when an experiment is obsolete. Availability language should be maintained rather than becoming a permanent promise, and the about route should avoid exposing private contact or employment details.
Plan for projects without imagery, long technical explanations, code snippets, external work that disappears, and a portfolio with only one case study. Ensure focus order and reading structure survive visual rearrangement. The owner remains responsible for image rights, analytics consent, inquiry handling, and factual outcome claims.
Name the person responsible for availability, case-study corrections, note archives, inquiry delivery, and third-party links. Keep source copies of approved text and media in recoverable storage, and verify that rollback does not resurrect a withdrawn client project or obsolete contact claim. Monitoring should report publication failures without sending private draft content to external logs.
Source-free preview
No public preview is published. Preview metadata remains private until release readiness and boundary review are complete.
Availability boundary
Implemented does not mean verified, release-ready, entitled, sold, or deployed. Manual browser and assistive-technology review, approved commercial terms, a protected archive, and server-side entitlement delivery remain required.