Michael D'Angelo: Personal Site

The source for mldangelo.com, a portfolio, résumé, project archive, and writing site built with Next.js, React, TypeScript, and Tailwind CSS.

The architecture is reusable and MIT licensed. The content and visual design are personal, so a fork needs a full rebrand.

Visit the live site →

• A statically exported Next.js 16 site deployed to GitHub Pages.
• A responsive light/dark design system built from semantic CSS tokens.
• Markdown writing with drafts, RSS, and page metadata.
• A filterable résumé that still prints in full.
• Tests for components, content, metadata, and the final static export.

Open your fork in a coding agent and ask:

Read AGENTS.md, use the Node version in .nvmrc, install the locked
dependencies, and start the development server. Do not change the site yet.
Tell me the local URL and report any setup failure with its exact output.

With GitHub CLI and nvm installed:

gh repo fork mldangelo/personal-site --clone
cd personal-site
nvm install
npm ci
npm run dev

If you use another version manager, choose a release accepted by engines.node in package.json.

1. Click Fork at the top of this page.
2. In your fork, click Code, choose Codespaces, then create a codespace.
3. Run:

nvm install
npm ci
npm run dev

Codespaces provides the tools, so you do not need to install them locally.

When you are ready to customize the site, give the agent your résumé, profile details, links, images, and intended site URL. Try:

Read AGENTS.md and docs/adapting-guide.md, set up the repository, then rebrand
this fork for [NAME] with the details and assets I provide. Work on a topic
branch and preserve the current routes and design unless I say otherwise.
Inventory the existing posts, external writing, résumé, and projects before
changing the shared identity. Do not relabel that content as mine. Ask whether
unmatched personal content should keep its original attribution, be replaced,
or be removed. Use the guide's reference map to update every identity surface
and generated asset. Search for remaining upstream details and run the full
validation suite. Do not commit, push, merge, change GitHub settings, create
secrets, or modify DNS. Report the external steps that remain.

The adapting guide has focused prompts for writing, feature removal, visual changes, and deployment, plus a map of the files an agent should inspect.

npm run dev             # Start the development server
npm run format          # Format with Prettier and Biome
npm run lint            # Run Biome checks
npm run type-check      # Run TypeScript
npm test                # Run Vitest
npm run build           # Build the production static export
npm run verify-export   # Inspect the generated HTML and XML
npm run og              # Regenerate the share card
npm run og:check        # Verify the committed share card is current

CI checks formatting, linting, types, the share card, tests, the production build, and the exported site on every pull request.

Pushes to main deploy the same static build that CI validates. See the adapting guide for URL and domain setup.

See the contributing guide for setup, branch and commit conventions, validation, and pull request expectations.

MIT. Use it however you want.