YAML-driven CV rendered to PDF via RenderCV using the Harvard theme.
uv tool install "rendercv[full]"rendercv render Luis_Ibarra_CV.yamlOutput lands in rendercv_output/.
rendercv render Luis_Ibarra_CV.yaml --dont-generate-markdown --dont-generate-htmlrendercv render Luis_Ibarra_CV.yaml --watchrendercv render Luis_Ibarra_CV.yaml --dont-generate-pdf --dont-generate-html --dont-generate-markdown| File | Description |
|---|---|
*.pdf |
Final CV |
*.typ |
Typst source — editable for advanced layout tweaks |
*.png |
Page previews |
All content and design live in Luis_Ibarra_CV.yaml. The # yaml-language-server comment at the top of the file enables schema autocomplete and validation in VS Code and other editors.
Every push is rendered by GitHub Actions and published to Cloudflare Pages over its global CDN. The bare deployment URL serves the PDF inline (a web/_redirects rewrite maps / → /cv.pdf).
Branch = job application. A CV tailored to a specific application lives on an application/* branch and gets its own URL:
main→ the canonical CV on the production (and custom) domain.application/<name>→ a preview athttps://application-<name>.rendercv.pages.dev.
Only main and application/* branches deploy — scratch branches don't generate previews.
Tailor a CV for a role:
git switch -c application/acme-devops
# edit Luis_Ibarra_CV.yaml (headline, highlights, …)
git push -u origin application/acme-devopsThe Actions run posts the preview URL to its job summary. main stays untouched.
- Create a Cloudflare API token with Account → Cloudflare Pages → Edit, and note your Account ID.
- Create the Pages project once (name must match
--project-namein the workflow):wrangler pages project create rendercv --production-branch=main
- Add the repo secrets
CLOUDFLARE_API_TOKENandCLOUDFLARE_ACCOUNT_ID(Settings → Secrets and variables → Actions). - (Optional) Attach a custom domain to the project's production deployment in the Pages dashboard.