dozens
/
resume.toml
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
resume builder with toml and groff
3 Commits
1 Branch
0 Tags
104 KiB
JavaScript 57.6%
Roff 42.4%
 
 
Go to file
Dozens B. McCuzzins 9d0088a601 Add many roles per company 
This change to the resume schema allows you to list multiple roles per
company in your work experience.
 		2024-01-04 14:46:10 -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 many roles per company 2024-01-04 14:46:10 -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 many roles per company 2024-01-04 14:46:10 -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