Dozens B. McCuzzins
e2e8198be5
This splits each resume section out into its own table (instead of having one long continuous table) and then puts each section in a keep. This fixes it so that no section is spread awkwardly across multiple pages. minor updates for formatting |
||
---|---|---|
LICENSE | ||
README.md | ||
example.pdf | ||
example.toml | ||
justfile | ||
lambdas.js | ||
resume.template | ||
schema.json | ||
view.js |
README.md
resume.toml
Movitation
-
Keep your resume in plain, organized, highly-editable text.
-
Separation of concerns: write content first. worry about formatting later.
-
Version control: keep your resume text in a git repository. track your changes. create new branches for large edits or for tailoring your resume while applying to a specific role.
About
This is a resume builder.
Data is stored in resume.toml
.
It is validated against jsonresume's json-schema.
And it is extracted as json with taplo.
It is converted to groff markup via mustache templates, and then exported to pdf.
You Will Need
- groff 1.23.0: for typesetting and pdf output (with the ms macro package; it should be installed anywhere groff is installed)
- mustache.js 4.2.0: for templates
- taplo 0.8.1: toml toolkit. Provides conversion to JSON, formatting, and validation.
- jq 1.6: json queries
- (optional) just 1.14.0: just a command runner
Getting Started
- Edit
example.toml
- Run
just pdf
- View pdf
Frequently Questioned Answers
- Why TOML?
- Because YAML is a drag.
- Because JSON, while highly serializable, is highly annoying to write with its strict, verbose syntax.
- Because while I love GNU Recfiles, they are just a little too annoying to query