Personal Portfolio

Portfolio Architecture Snapshot

My previous portfolio was a rigid single-page build that made adding experiments painful, so this iteration focuses on extensibility first and polish second.

Goals

• Ship a performant, animation-rich portfolio on the latest Next.js App Router stack.
• Keep content authoring simple via MDX while enforcing validation.
• Showcase experiments, extras, and project write-ups with consistent UI primitives.

Stack Highlights

Component Sketches

// simplified MDX loader wiring
export async function getAllContent(type) {
const entries = await loadAllContent(type)
return entries.map((entry) => ({
  ...entry,
  isPlaceholder: entry.title.endsWith('(Work in Progress)'),
}))
}

Roadmap

• Document the motion system (Framer Motion + intersection observers).
• Add a section on the embedded OG image generator.
• Publish performance metrics and accessibility checks.

Content Authoring Process

Writing new project or extra entries stays intentionally lightweight:

1. Create an .mdx file under content/projects or content/extras.
2. Populate front matter with the required fields (title, slug, date, tags, etc.). The Zod schema in lib/content.ts validates everything at load time.
3. Reference media with the /projects/<slug>/... paths emitted by the asset pipeline. Missing files automatically fall back to the gear placeholder.

Available MDX Components

By sticking to these primitives, every page inherits the same typography, spacing, and motion patterns—even when the underlying project is still a work in progress.

Obsidian Workspace (Work in Progress)

A look at my current Obsidian vault organization and daily note workflow.

Extra•2024-05-08•Obsidian

Neovim Setup (Work in Progress)

Plugins, keymaps, and workflow choices in my Neovim setup.

Extra•2024-05-01•Neovim