The dist/
directory contains assets that are deployed for the website
as-is. The dist
directory acts as a staging directory - the generated
index.html
would exist at the root of this.
I deploy to S3 and my local Gemini and Gopher servers.
You might consider JSON Resume instead.
I didn't develop this for general use in mind, but feel free to take what you
want from it. You'd probably want to modify the resume.py
script, the
templates/
, and the resume.yaml
, of course.
Use the Makefile
to build the resume.
To build all formats:
make
To build HTML only:
make html
The GitHub Workflow builds and deploys my resume.
My resume is published to the S3 website bucket for joshbeard.me.
It's also useful for local development to preview the site with an actual HTTP server rather than as a local file, which is helpful for testing relative URLs and the like similar to 'production'.
make serve
Visit the local instance via http://localhost:8080/resume/
- GitHub Workflows for build and deployment.
- Pandoc for generating Word documents.
- GitHub action for headless Chrome for generating the PDF document.
- minify-action for minifying static documents.
- AWS S3 and CloudFront for hosting.
I've maintained my resume in different ways over the years, more recently in
simple HTML. I hate using word processors and their nightmare document formats.
I want a website version, but I also wanted a PDF and Markdown copy. For fun,
I generate it in several formats, including some more esoteric ones like
a man page, finger [email protected]
, and Gemini