https://github.com/jpcercal/resume
João's Resume JSON/PDF Builder
https://github.com/jpcercal/resume
curriculum cv resume-builder resume-creator resume-generator resume-parser resume-template
Last synced: 3 months ago
JSON representation
João's Resume JSON/PDF Builder
- Host: GitHub
- URL: https://github.com/jpcercal/resume
- Owner: jpcercal
- License: mit
- Created: 2016-04-01T12:38:37.000Z (about 10 years ago)
- Default Branch: main
- Last Pushed: 2025-01-15T13:32:07.000Z (over 1 year ago)
- Last Synced: 2025-01-15T15:22:24.286Z (over 1 year ago)
- Topics: curriculum, cv, resume-builder, resume-creator, resume-generator, resume-parser, resume-template
- Language: SCSS
- Homepage:
- Size: 12.5 MB
- Stars: 4
- Watchers: 1
- Forks: 2
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Resume
[](https://github.com/jpcercal/resume/blob/main/resume.pdf) [](https://raw.githubusercontent.com/jpcercal/resume/main/resume.pdf) [](https://raw.githubusercontent.com/jpcercal/resume/main/resume.json) [](https://github.com/jpcercal/resume/actions) [](https://github.com/jpcercal/resume/actions/workflows/resume.yml?query=branch%3Amain) [](https://github.com/jpcercal/resume/releases) [](https://hub.docker.com/r/jpcercal/resume) [](https://nodejs.org/)
As a software engineer with a thirst for adventure, I'm constantly looking for ways to
apply engineering rigour to problems that most people solve manually. A resume is one of
those problems. It goes stale, the formatting drifts, version history disappears into a
graveyard of `final_v3.docx` files, and every update turns into a tedious afternoon of
pixel-pushing. I decided to treat my resume the same way I treat production software:
as source code, with automation, versioning, and a proper release pipeline. This
repository is the result.
## Why your resume deserves a repository
The instincts that make engineers effective — reproducibility, automation, auditability —
apply just as well to a resume as they do to any other deliverable. Here is why I think
every engineer should have one of these:
**Your resume is source code.** The single source of truth lives in `resume.json`, a
structured file that follows the open [JSON Resume](https://jsonresume.org/) schema. Every
change is a commit. The full history is preserved. There are no conflicting copies,
no formatting accidents, and no mystery about what changed between versions.
**Every push ships a release.** The moment you push, the CI pipeline takes over. It builds
a Docker image, renders the HTML, generates the PDF, minifies the page, deploys it to
GitHub Pages, force-amends the commit to include the built artifacts, and tags a new
versioned release — all without you touching a single tool manually. The pipeline does
in seconds what used to take an afternoon.
**One Docker command, anywhere.** The build is fully containerised and produces identical
output on Intel, Apple Silicon, and ARM servers. There is no "it works on my machine"
problem. Anyone can clone the repo, run a single command, and have a pixel-perfect PDF
in their working directory.
## How does it work?
The pipeline is intentionally simple:
| Step | What happens |
|------|--------------|
| Edit `resume.json` | Update your content — work experience, skills, education |
| `git push` | Triggers the GitHub Actions workflow |
| CI builds the image | Multi-arch Docker image pushed to Docker Hub |
| Artifacts are generated | `resume.pdf`, `resume.html`, and two preview PNGs |
| HTML is minified | CSS, JS, and whitespace compressed for the web |
| GitHub Pages is updated | The minified HTML is live at your Pages URL |
| Release is tagged | A versioned GitHub release is created with `resume.pdf` as an asset |
Under the hood, [resumed](https://github.com/rbardini/resumed) validates the JSON and
renders it through a custom [Handlebars](https://handlebarsjs.com/) template styled with
[TailwindCSS v4](https://tailwindcss.com/). [Puppeteer](https://pptr.dev/) then takes the
HTML and prints it to PDF using a headless Chromium instance baked into the Docker image.
No external services, no proprietary tooling — just open-source software running in a
reproducible container.
## See it in action
At the very top of this page you can click `João's Resume | VIEW` to open the PDF directly
in your browser, or `João's Resume | DOWNLOAD` to save a copy for offline viewing.
> For the tech-savvy, the raw data is in
> [`resume.json`](https://raw.githubusercontent.com/jpcercal/resume/main/resume.json) —
> the file that drives everything. Here is a preview of what it looks like:
>
> 
> The full workflow is defined in `.github/workflows/resume.yml`. You can watch it run
> live on [GitHub Actions](https://github.com/jpcercal/resume/actions).
## Build it yourself
The only dependency is [Docker](https://www.docker.com/). Once installed, you have two
options:
**Option 1 — Pull the pre-built image from Docker Hub (fastest):**
```bash
docker pull jpcercal/resume
```
**Option 2 — Build the image locally (after making changes to the `Dockerfile`):**
```bash
docker build --tag jpcercal/resume .
```
Either way, generate all artifacts with a single command:
```bash
docker run --rm -v "$PWD:/app" jpcercal/resume
```
> **Windows PowerShell:** replace `"$PWD"` with `"${PWD}"`.
This mounts the project root as `/app` inside the container and writes four files directly
into your working directory:
- `resume.pdf`
- `resume.html`
- `resume-preview.pdf.png`
- `resume-preview.json.png`
The image is built for both `linux/amd64` and `linux/arm64`, so it runs natively on
Intel/AMD machines as well as Apple Silicon (M-series) and ARM servers — no emulation
overhead.
Enjoy it. =)
## Fork it and make it yours
The best part about treating a resume as a repository is that the whole pipeline is
forkable. Clone or fork this repo, edit `resume.json` with your own information, push,
and your personal resume pipeline is live — complete with GitHub Pages hosting, versioned
PDF releases, and a Docker image on Docker Hub.
If the default layout does not suit your style, the entire theme lives in the `theme/`
folder: swap the Handlebars template, adjust the TailwindCSS tokens, add new helpers.
The `resume.json` data model stays the same; only the presentation changes.
Your resume is a living document. It should be treated like one.