This repo contains the source for my personal CV
A website (Svelte) and PDF (LaTeX) auto-built from jsonresume data
π danielwambua.dev | π Daniel-Wambua-CV.pdf
To automate my CV generation, and make it easier to maintain. All content defined in YAML, then a script generates a LaTeX PDF and deploy a web version. I did it this way so that I don't need to f**k around with Microsoft Word.
About the Developer
Professional Background
I'm an Information Technology student with a strong focus on cybersecurity, offensive security, and vulnerability assessment. My experience includes hands-on work in penetration testing labs, CTF competitions, and security tooling. I am passionate about learning, security research, and building systems that automate and simplify technical workflows. You can find my open source projects on GitHub and learn more at danielwambua.dev.This CV automation project reflects my philosophy: why spend time on repetitive tasks when you can build systems that work for you? The entire CV generation pipeline is designed for maximum efficiency and maintainability.
The resume content is defined in resume.yml following the jsonresume.org standard, and validated against schema.json.
A LaTeX document is then generated from template.jinja formatted with resume-format.cls, which is then compiled into a PDF by GitHub Actions, and published under the Releases tab.
The system features automatic PDF generation through a web download endpoint - when you visit the download link, the PDF is dynamically generated from the YAML source, ensuring it's always up-to-date. A markdown version is also generated by lib/markdown.py, as well as a CV website which is built as a static site with SvelteKit, and deployed to GitHub Pages and Vercel, at cv.danielwambua.dev.
The entire pipeline is optimized for content accuracy and layout precision, with automatic handling of link overflow and content formatting to ensure professional presentation.
Why? ...Because why spend 30 minutes writing your CV, when you could spend 30 hours automating it, obviously!
- Fork the repo
- Update resume.yml with your own content
- Create a tag, or trigger the GH actions workflow
- ....and a PDF and website gets magically generated
Workflows
See the Makefile for all the available commands. Or, just run make from the root, to install deps, validate content, generate LaTeX, and compile PDF
- Clone the repo
- Update resume.yml with your own content
- Run
makefrom the root, to install deps, validate content, generate LaTeX, and compile PDF
Or, to deploy the web version
- Follow steps above (clone, edit, validate)
- Run
make webto generatedist/ - upload to any CDN, web server or static hosting provider (I use Vercel)
Commands
make install- Download dependenciesmake validate- Validate contentmake generate- Generate LaTexmake compile- Compile PDFmake clean- Remove generated filesmake watch- Watch for changes, recompile and refreshmake web- Launches web version, installs NPM deps, builds and serves the site
flowchart LR
GA([π€ GitHub Actions<br><sup>Triggered on <code>resume.yml</code> change</sup>]) --> A3
A1([π Start<br><sup>Clone repo & cd into it</sup>]) --> A2[βοΈ Update <code>resume.yml</code><br><sub>Your resume content goes here</sub>]
A2 --> A3[β
make validate<br><sub>Check for content or schema issues</sub>]
%% PDF PATH
A3 --> PDF[π PDF Output]
PDF --> B1[π¦ make install<br><sub>Install all dependencies</sub>]
B1 --> B2[π make generate<br><sub>Generate LaTeX from resume.yml</sub>]
B2 --> B3[π make compile<br><sub>Compile LaTeX to PDF</sub>]
B3 --> B4([β
View at <code>out/resume.pdf</code>])
%% WEB PATH
A3 --> Web[π Website Output]
Web --> C1[π make web<br><sub>Build static site into <code>./dist</code></sub>]
Web --> C2[π§ͺ make web_dev<br><sub>Start local dev server at <code>localhost:5173</code></sub>]
C1 --> C3([π Deploy <code>./dist</code> to your host])
C2 --> C4([π View site locally in browser])
Modify data by editing resume.yml
If you need to customize the layout, edit template.jinja
Or to change the styles and formatting, edit resume-format.cls
All the scripts used to generate output are located in lib/
These are triggered either by the Makefile or via GitHub Actions with the workflows/
The source for the website version is located in web/
No point contributing. Just fork the repo and do whatever changes you like there.
No point in raising issues here. It works on my machine. Therefore I see no issue, lol
This project uses the following open-source libraries and resources:
Daniel Wambua/CV is licensed under MIT Β© Daniel Wambua 2025.
For information, see TLDR Legal > MIT
Expand License
The MIT License (MIT)
Copyright (c) Daniel Wambua <daniel@wambua.com>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sub-license, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished
to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included install
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANT ABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Β© Daniel Wambua 2025
Licensed under MIT
Thanks for visiting :)


