Add /work: stylized case-study section - #56
Draft
amyrlam wants to merge 5 commits into
Draft
Conversation
Adds a `work` content collection, /work listing, and /work/[slug] page for portfolio-style case studies — more layout freedom than the blog's plain-prose template, and separate from it since these are meant to read as stylized stories rather than chronological posts. First entry (design-tokens.md) is a draft placeholder outlining the design-token PR (#40) as the first piece: "how this site is built," proven live via /design-system rather than screenshots. A second entry on an Adobe project is planned to follow in the next week or two. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
"Case studies" sets the right expectation (in-depth narrative, not a project grid) and reads naturally next to a future private/password- protected entry. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Replaces the outline placeholder with a full working draft, written to PRODUCT.md's voice rules (sentence-case prose, no resume speak). The arc: why a computed sky instead of a theme, how build-enforced AAA contrast became the design engine, the weather-vs-fixed color split that made the polaroid the one named exception, the token layer from PR #40, and what transfers to team-scale work. Stays draft: true until the words are approved. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Feedback-driven revision: the first draft was long and token-centric. This one covers the site's full story (the geo lookup and "borrowed sky" honesty, real stars, quarter-hour hops, the secret shows, the static-plus-one-function deploy) while cutting overall length ~20%. The tokens shrink to one section, with color-format-agnostic wording plus an oklch mention so the prose survives PR #57's hex-to-oklch conversion. New "objects under the sky" section names the two print mountings (lightbox polaroids vs. the taped dinghy print) as one deliberate family rather than an inconsistency. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The upcoming case study covers how this site is built, which makes this link redundant once it publishes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
No issue for this yet — opening as a draft so it's trackable on the project board while content and structure are still being worked out.
workcontent collection (src/content.config.ts), separate from thebloginfra in Add blog infrastructure #9. Case studies are meant to read as stylized, freeform stories rather than chronological posts, so they get their own section instead of living in the blog./worklisting +/work/[slug]page, reusing the site's.sky-card/token system but with more layout room than the blog template.workadded to the homepage footer nav, alongsideabout/contact.design-tokens.md,draft: true) outlining the first real case study: the design-token pipeline from Add design tokens, flesh out /design-system #40, framed as "how this site is built" — provable live via/design-systemrather than screenshots. A second entry on an Adobe project is planned within the next week or two.Open questions (tracking here, not blocking the scaffold)
/workvs/case-studiesvs something else./design-system)./design-system— case study should link out to it, not duplicate it./workand/blog(once Add blog infrastructure #9 merges) should cross-link or stay fully separate.Test plan
npm run build— 6 pages generate, including empty/work(placeholder isdraft: true)worknav link,/workrenders the empty state correctly🤖 Generated with Claude Code