Portfolio Redesign Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Build a modern, premium redesign of the existing Jekyll portfolio while preserving routes, content collections, and the original monochrome/blue aesthetic.

Architecture: Keep the Jekyll site static and data-driven. Add structured YAML for experience and research, one global redesign stylesheet, and targeted Liquid markup updates for each page family.

Tech Stack: Jekyll, Liquid, Sass/CSS, static assets, Node.js verification script.


Task 1: Verification Harness

Files:

Create a Node.js script that checks for the new CV asset, global CSS, page classes, timeline data, research data, CV nav link, project cards, skill groups, tag cloud, and 404 shell.

Run: node scripts/verify-redesign.js Expected: failure listing missing redesign features.

Task 2: Data and Assets

Files:

Task 3: Global Visual System

Files:

Task 4: Page Redesign

Files:

Task 5: Verification and Sync

Files: