content: fix Function 03 Labs start date and flag remaining CV gaps - #72
Conversation
Corrects the Function 03 Labs entry (CV + portfolio timeline) to start in 2021 and reflect part-time status while studying, per issue #66 - it was incorrectly showing a 2023 start and full-time type. Also flags the remaining CV/timeline content (Harmonia, The Fund, Digital Army date conflict, JobFlow, Kenny, Zero Locker, case-study linking) as explicit TODOs rather than guessing at real copy, since only structural/factual corrections are safe to make without Malek's input.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 27 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
|
Per owner request, resume.json should not be edited by automated CV work. Function 03 Labs date fix and Digital Army note stay in the .mdx work entries only.
1 participant
Part of #66.
What this does
data/resume.jsonanddata/work/3-function03-labs.mdx) to start in 2021 instead of 2023, and marks it part-time, per the explicit correction in content: update CV and professional experience timeline #66 (Malek worked there part-time while studying). The exact starting month is unconfirmed - the original month (June) was kept as-is with aTODO(#66)comment flagging it for verification, since only the year was stated as fact in the issue.TODO(#66)note ondata/work/5-digital-army.mdxflagging that the issue's approximate Digital Army range (~2021-2023) conflicts with the existing entry's dates (Feb-Apr 2023) - left unchanged pending Malek's confirmation.TODO(#66)comment inactions/content-collections.tsexplaining why new work entries (Harmonia, The Fund) aren't added yet: every field in the work schema is required andoverview/positionrender directly on the public timeline, so a stub with placeholder copy would ship fabricated-looking text to visitors.metadata.notesfield indata/resume.json(an existing, unused schema field - not rendered anywhere in the app) listing everything still blocked on real content from Malek.Education section condensing was already handled in #69 (merged) - this PR builds on top of that and doesn't touch it further.
Still needed before #66 can close
These need real facts/dates/wording from Malek - not guessed at here:
Verification
data/resume.jsonvalidated as JSON.pnpm build: content-collections parses all 19 documents cleanly (schema still valid withtype: "part-time"), TypeScript compiles clean. Build then fails during static generation of/, but only on the known pre-existing missing Spotify/GitHub/Groq/Resend env vars - unrelated to this change, not introduced by it.eslint .: no new issues in any of the four changed files (pre-existing unrelated lint errors exist elsewhere in the repo, untouched by this PR).