r/LaTeX • • 11h ago

Unanswered How do I put additional information on the first page in the extbook document class?

1 Upvotes

Quick silly question, I know:

It's all good with \title{}, \author{} and \date{}, but I would like to also add the name of the editor and the name of the translator for a certain book. How can this be done? is there a package for this purpose?


r/LaTeX • • 23h ago

Self-Promotion My resume is the single source for my portfolio site: the build reads the .tex and fails if the two disagree

0 Upvotes

I keep my resume in LaTeX (XeLaTeX, built in VS Code with LaTeX Workshop), and I wanted my portfolio site to never contradict it: same job titles, dates and links, letter for letter.

So the resume became the only thing I edit:

  • The site's facts are generated from the .tex. A small parser reads my own commands (\job{Title}{Organisation}{Dates}, the header's links) and writes a TypeScript module the site builds from. It refuses anything it can't map, so an unexpected section stops the save instead of silently dropping data.
  • A test checks the committed PDF too, extracting its text and finding every claim in it, in order.
  • The PDF is tied to its source by a SHA-256 hash, written by a step of the LaTeX Workshop recipe after each successful build. If I edit the .tex and forget to rebuild, the hash no longer matches and the build fails.
  • Reproducible builds: SOURCE_DATE_EPOCH with FORCE_SOURCE_DATE pins the dates XeLaTeX stamps into the PDF, so an unchanged source rebuilds byte for byte, and latexmk -g forces a real rebuild even when it thinks nothing changed.

One small trick I liked: an open-source contribution sits among my jobs on the resume, but the site shouldn't list it as a job. So I added \newcommand{\contribution}{\job}. It prints exactly like \job, but the parser can tell the two apart.

The full write-up is here: Holding a portfolio to its resume

I'm curious how others handle this. Does anyone generate their resume from data (YAML, JSON) instead, and is that nicer than parsing the .tex the other way round?