Skip to main content

Feature: Landing Page (/)

Purpose​

  • Feature name: Landing page (/)
  • Why this feature exists: Provide a fast reviewer entry point that explains how to evaluate the portfolio and links directly to evidence.

Scope​

In scope​

  • hero narrative and value proposition
  • reviewer evaluation path callout
  • primary calls to action (CTAs)
    • e.g. CV, Projects, Evidence Docs
  • featured work highlights

Out of scope​

  • global navigation and footer (covered in Navigation and UX polish)
  • theme management (covered in Theming and accessibility)

Prereqs / Inputs​

  • NEXT_PUBLIC_DOCS_BASE_URL configured for evidence links
  • optional NEXT_PUBLIC_GITHUB_URL and NEXT_PUBLIC_LINKEDIN_URL

Procedure / Content​

Feature summary​

  • Feature name: Landing page (/)
  • Feature group: Core pages and reviewer journey
  • Technical summary: Server-rendered Next.js route that composes CTA buttons, evidence callouts, and featured project cards using shared layout components.
  • Low-tech summary: The home page tells reviewers what to look at first and gives quick links to proof.

Feature in action​

  • Where to see it working: / in the deployed app or http://localhost:3000/ during pnpm dev.

Confirmation Process​

Manual​

  • Steps: Open /, click “Start with the CV,” “Browse projects,” and “Open evidence docs.”
  • What to look for: Internal CTA routes load correctly; evidence links render with expected labels and non-empty href attributes; featured cards show dossier links.
  • Artifacts or reports to inspect: Optional Playwright E2E runs in CI showing core route coverage.

Tests​

Potential behavior if broken or misconfigured​

  • Evidence links route to the wrong docs base URL.
  • CTAs are missing or point to invalid routes.
  • Featured work section shows empty or stale content.

Long-term maintenance notes​

  • Keep the evaluation path aligned with the reviewer guide and evidence structure.
  • Update featured work as projects change or new gold-standard entries exist.

Dependencies, libraries, tools​

  • Next.js App Router
  • React
  • Tailwind CSS

Source code references (GitHub URLs)​

ADRs​

  • None.

Runbooks​

  • None.

Additional internal references​

Validation / Expected outcomes​

  • Reviewers can reach /cv, /projects, and docs within two clicks.
  • Evidence callouts match the current documentation structure.

Failure modes / Troubleshooting​

  • Docs links broken: verify NEXT_PUBLIC_DOCS_BASE_URL and redeploy.
  • Empty featured cards: verify project registry content and rebuild.

References​

  • None.