resume builder with toml and groff
 
 
Go to file
Dozens B. McCuzzins e2e8198be5 Add keeps to resume sections
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
2024-02-05 10:55:03 -07:00
LICENSE first commit 2023-12-05 22:51:32 -07:00
README.md Add mustache lambdas 2023-12-21 19:51:26 -07:00
example.pdf Add keeps to resume sections 2024-02-05 10:55:03 -07:00
example.toml Add many roles per company 2024-01-04 14:46:10 -07:00
justfile Add many roles per company 2024-01-04 14:46:10 -07:00
lambdas.js Add mustache lambdas 2023-12-21 19:51:26 -07:00
resume.template Add keeps to resume sections 2024-02-05 10:55:03 -07:00
schema.json first commit 2023-12-05 22:51:32 -07:00
view.js Add many roles per company 2024-01-04 14:46:10 -07:00

README.md

resume.toml

Movitation

  1. Keep your resume in plain, organized, highly-editable text.

  2. Separation of concerns: write content first. worry about formatting later.

  3. 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

  1. groff 1.23.0: for typesetting and pdf output (with the ms macro package; it should be installed anywhere groff is installed)
  2. mustache.js 4.2.0: for templates
  3. taplo 0.8.1: toml toolkit. Provides conversion to JSON, formatting, and validation.
  4. jq 1.6: json queries
  5. (optional) just 1.14.0: just a command runner

Getting Started

  1. Edit example.toml
  2. Run just pdf
  3. 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