Back to projects

Personal knowledge and case-study CMS

Portfolio Content System

A server-rendered portfolio architecture that keeps project data in Notion while preserving a fast custom frontend.

Outcome

Creates a maintainable publishing workflow for case studies, experiments, and technical notes without exposing Notion credentials.

Problem

The previous one-page portfolio looked polished but did not provide enough depth for senior engineering evaluation.

Approach

Split the site into focused routes, moved content into server-loaded project records, and added a lightweight systems interaction to explain the positioning.

Architecture

SvelteKit routes call server-only Notion modules. Components render local design, cards, motion, and Notion blocks without exposing tokens to the browser.

Result

A deeper portfolio structure that is easier to evaluate, edit, and deploy.

Lessons learned

A senior portfolio should show constraints and decisions, not just outcomes and logos.

Constraints

  • Keep SvelteKit and working code.
  • Keep Notion API calls server-side only.
  • Avoid heavy animation dependencies and scroll hijacking.

Technical decisions

  • • Use server load functions for CMS access.
  • • Provide local fallback content for reliable builds.
  • • Use CSS/SVG motion instead of heavier 3D.

Key features

  • • Case-study routes
  • • Notion-backed project listings
  • • AI Systems Map