This repository is the source and documentation hub for a GitHub Pages project that publishes multiple resume variants generated from one canonical resume input and one shared prompt. The live site is intentionally separate from this repository README: the site landing page routes viewers to the right resume experience, while this README explains how the repository is organized.
The project compares resume outputs generated with the same source data and prompt across a spectrum of model/tooling configurations:
- Frontier hosted models for the site shell and gold-standard resume.
- Hosted open-weight models for strong non-frontier comparisons.
- Local offline small language models for VRAM-constrained generation.
- A deterministic baseline for regression checks.
All variants use the same platform, source resume, prompt template, validation rules, and publishing pipeline.
Resumeroutes to the YAML-configured gold-standard resume.Resume Galleryroutes to a gallery of resume pages generated by different models from the same source data and prompt (inputs/resume.yaml+inputs/prompt.md), viascripts/generate-gallery-page.mjs.- Resume pages, role routing, metadata, and PDF links are driven by
config/site.yamlandconfig/resumes.yaml.
npm install
npm run dev
npm test
npm run buildThe GitHub Pages site starts with a role selector, not this README.
flowchart TD
A[Site Home] --> B{Viewer Role}
B -->|Resume| C[Gold Resume]
B -->|Tech| D[Resume Gallery]
D --> E[Variant Detail]
E --> F[Markdown]
E --> G[PDF]
The two role buttons must use short labels:
Resume GalleryResume
Resume goes directly to the configured gold-standard resume. Resume Gallery opens a configurable gallery of all resume variants.
Dense project documentation lives in docs/:
- TypeScript for orchestration and validation.
- Astro for the GitHub Pages static site.
- YAML for site routing, resume registry, model matrix, and gold-standard selection.
- Markdown as the canonical future LLM resume output.
- HTML and PDF as rendered publication formats.
.
├── README.md
├── docs/
├── config/
│ ├── site.yaml
│ └── resumes.yaml
├── src/
│ ├── pages/
│ ├── components/
│ ├── layouts/
│ └── lib/
├── public/resumes/
├── tests/
└── .github/workflows/
- Adding or removing a resume should be a YAML-only registry change when assets already exist.
- The site shell and gold-standard resume are generated or refined by a frontier model, with their provenance recorded.
- The
Resumepath has happy-path and sad-path tests. - The role-selector landing page has happy-path and sad-path tests.
- Model runners are loosely coupled from rendering, routing, validation, and deployment.