markstuart.dev

The source for markstuart.dev, Mark Stuart's personal site. It is built with Next.js 16, React 19, TypeScript, and Tailwind CSS.

The source code, tests, build configuration, automation, and project documentation are available under the MIT License. This remains a personal site: that license does not cover Mark's identity, biography, editorial writing, or original artwork. Read NOTICE and the asset-rights ledger before copying or publishing any part of the repository.

Use exactly Node 24.19.0 and npm 11.19.0. The versions are declared in .node-version, package.json, and package-lock.json.

npm ci
npx playwright install chromium
cp .env.example .env.local
npm run runtime
npm run dev

The site is available at http://localhost:3000. The home page begins at app/(site)/page.tsx, with shared site layout in app/(site)/layout.tsx. Public pages render without provider credentials; add only the blank variables from .env.example needed for the capability under test.

Run npm run help for the command index. The primary commands are:

CI runs the complete gate and uploads Playwright diagnostics. Separate weekly workflows audit production dependencies and check public links. Action versions are pinned to immutable commits and maintained by Dependabot.

• lib/data/resume.ts is authoritative for biography, role history, and career claims. Other curated lists must not contradict it.
• Local writing lives in content/posts/*.mdx; external writing links live in lib/data/writing.ts.
• Static assets live under public/ and require a corresponding rights review.
• PRODUCT.md records durable product truth, and DESIGN.md records the incumbent visual system and tokens.

To publish an MDX post, create content/posts/<slug>.mdx with title, date, description, and sample frontmatter. Use an ISO YYYY-MM-DD date. A sample post must never trigger subscriber mail. Run npm run check and review the rendered post, index, feed, metadata, and links before publishing.

All supported variables are listed blank in .env.example. The complete capability matrix, webhook verification details, retry and reconciliation rules, deployment checks, rollback procedure, and secret rotation order are in the operations runbook.

Before making a fork public:

1. Replace the site owner's name, biography, resume, writing, portraits, and site identity.
2. Remove or replace every asset whose transferable rights are not documented in docs/asset-rights.md; do not imply endorsement by an employer, publication, conference, or product vendor.
3. Replace production URLs, analytics, email identities, webhook endpoints, cron configuration, and provider projects with accounts you control.
4. Review the entire Git history for secrets and private content. Deleting a file in the latest commit does not remove it from history.
5. Keep .env files and credentials untracked, run npm run policy, and run the complete npm run check gate.

See CONTRIBUTING.md for changes, SECURITY.md for private vulnerability reports, SUPPORT.md for help, and docs/contributor-tooling.md for vendored agent skills and Windows symbolic-link behavior.