content(resume): reposition Portfolio Template entry as drift-killer#26
Merged
Merged
Conversation
Old highlights sold the visual modes (two views, scroll animations, PWA) but buried the actual product story — that this is a single source of truth ending the resume↔website drift problem. New three bullets lead with that pain + solution, then list the features as a tight zero-code value prop, then keep the existing CTA. Trimmed total length ~35% so the PDF doesn't overflow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Apr 27, 2026
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
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
Updates the
personal_projects"Portfolio Template" entry inresume.yamlto match the rebrand merged in PR #24. Old highlights sold the visual modes; new bullets lead with the resume↔website drift-killer story that birthed the project.Diff
Trimmed total ~35% (~250+250+150 → ~195+155+115 chars per bullet) so the PDF doesn't overflow.
Why this is a PR not a direct push
Per the MAINTAINER_GUIDE.md "Personal data update" flow, this would normally be a direct push to
personal. Doing it as a PR lets you eyeball the rendered PDF preview before deploy fires.Test plan
npm run hydrate && npm run buildlocally to render the PDF and confirm the 3 bullets fit cleanly without overflow