Feature EV charging data case study and surface projects earlier

[cbratkovics]

Motivation

• Surface stronger technical evidence earlier on the homepage by moving the project flashcards above Professional Experience and add a focused, recruiter-friendly case study for the new EV Charging project that preserves the site’s existing identity and component system.
• Present the independent project "EV Charging Data: Unified Schema" as a flagship featured project that demonstrates trustworthy data foundations, source-integration, intentional metrics, quarantine/reconciliation, and evidence-backed findings scoped to v0.1.0.

Description

• Added a data-driven project entry in portfolio/data/projects.ts for ev-charging-unified-schema and marked it featured: true so it renders as the flagship card in the canonical project collection.
• Implemented a dedicated internal case-study route at /projects/ev-charging-data-unified-schema in portfolio/app/projects/ev-charging-data-unified-schema/page.tsx, including canonical metadata, Open Graph/Twitter fields, accessible evidence links (repository, dbt docs, findings), the full approved case-study content, and a visible As of v0.1.0 scope line.
• Reordered homepage sections by moving Projects before Experience in portfolio/app/page.tsx, updated Navigation ordering in portfolio/components/Navigation.tsx, and added the new route to the sitemap in portfolio/app/sitemap.ts.
• Small UI/UX updates: added reusable ProjectAction handling and internal-link support in portfolio/components/Projects.tsx, created compact case-study helpers (EvidenceLinks, Section, FindingBlock) in the new page, and added scoped case-study CSS in portfolio/app/globals.css without changing the overall visual system.
• Kept the project-driven architecture intact (no parallel card system), preserved existing project identities, and included only the supplied quantitative claims exactly as scoped to v0.1.0.

Testing

• Ran publication and static checks with npm run check:publication and npm run check:publication:build, both of which passed.
• Ran code quality and verification commands npm run lint, npm run type-check, and npm test where npm test executed the content-contract suite (12 tests) and all passed.
• Built and exercised production routes with npm run build and npm run test:e2e, where the production build completed and the end-to-end checks (homepage order, sitemap, canonical metadata, and the EV case-study route) passed; all commands reported success in this environment.
• Attempted direct external URL status checks for the repository, dbt docs, and findings but the environment’s CONNECT proxy returned HTTP 403 so those remote checks could not be completed here; the links are present and open in new tabs from the site per site conventions.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
cbratkovics-dev	Ready	Preview	Sep 20, 2026 9:55pm UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-20T21:57:42.070611Z	e7188ee	PR opened
🔒 Security Review	✅ Completed 2026-09-20T21:57:02.864525Z	e7188ee	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e7188ee643

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve the social image in the case-study metadata

When this case-study URL is shared, the page-level openGraph and twitter objects replace the corresponding root metadata objects, so the generated HTML contains neither og:image nor twitter:image even though the Twitter card requests summary_large_image. Add an image to both page-level objects (or reuse the site's existing Open Graph image) so social crawlers can render the intended preview.

Useful? React with 👍 / 👎.