aprilrieger.github.io

Senior-level portfolio site built with Astro 6.2, MDX content collections, and Tailwind CSS. Static output goes to dist/ for GitHub Pages.

Requires Node 20+. This repo uses .npmrc with legacy-peer-deps=true so @astrojs/tailwind installs cleanly with Astro 6 until upstream peer ranges catch up.

Develop

npm install
npm run dev

Build

npm run build
npm run preview

Theme

Colors are semantic tokens in tailwind.config.mjs (canvas, surface, border, ink, accent). Edit the hex values there to re-skin the site.

Content

• Content collections: src/content.config.ts (glob loaders; Astro 6 format)
• Case studies: src/content/caseStudies/*.mdx
• Blog: src/content/blog/*.mdx
• Site metadata and nav: src/site.config.ts
• Static assets (images, resume PDF): public/

Replace public/April_Rieger_Software_Engineer_Resume_2026.pdf with your final resume.

Deploy (GitHub Pages)

This repo is set up for a user site at https://aprilrieger.github.io. site in astro.config.mjs must stay https://aprilrieger.github.io (no base path).

One-time GitHub settings

1. Repo Settings → Pages → Build and deployment.
2. Under Source, choose GitHub Actions (not “Deploy from a branch”).
3. Push main or using-astro; the workflow .github/workflows/deploy-pages.yml will build and publish dist/. (While the Astro branch is in flight, using-astro and main both deploy to the same site; after you’re done, remove using-astro from the workflow so only main deploys—see comments in that file.)

What the workflow does

• Push to main or using-astro: npm ci → npm run build → upload dist/ → deploy with actions/deploy-pages.
• Pull requests into main or using-astro: runs build only (no deploy).
• Workflow dispatch: run manually from main or using-astro to deploy that ref.

Publishing uses the same workflow as Astro’s GitHub guide. You can still run npm run deploy locally with gh-pages if needed; Actions is the recommended path.