This repo contains the source for my personal CV
A website (Svelte) and PDF (LaTeX) auto-built from jsonresume data
🌐 cv.aliciasykes.com | 📄 Alicia-Sykes-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.
Motive (legacy)
Backstory
I'm just about to be made redundant 😢 (Aug '24), which I am gutted about. I've never been laid off before, and I loved my job and the people I worked with. So I'm now on the market, looking for a new role!I've kept my CV/resume very brief, in an attempt respect the hiring manager's time. But in short, I'm an experienced, Principle-level full stack engineer with a love for quality, performance, mentoring, tech and open source. The best judge of a developer is their code, and while I cannot share what I've done professional or for private clients, I have got many open source projects on my GitHub and at apps.aliciasykes.com.
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 formated with resume-format.cls, which is then compiled into a PDF by GitHub Actions, and published under the Releases tab.
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.aliciasykes.com.
Why? ...Because why spend 30 minutes writing your CV, when you could spend 30 hours automating it, obviously!
- Fork the repo
- Update resume.json with your own content
- Create a tag, or trigger the GH actions workflow
- ....and a PDF and website gets magically generated
Workflows
| Workflow | Description | Status |
|---|---|---|
tag |
Creates a new Git tag. Optionally specify the tag name and description, or by default it will just bump the sem ver patch number by 1 | |
generate |
Generates your resume in PDF form as an artifact. If triggered by a tag, then a new release will be created, with the PDF attatched | |
validate |
Validates your resume data against the schema. This will also run whenever a new PR is opened, to ensure it's valid and working | |
mirror |
Backups up repository and content to our (non-Microsoft) Codeberg mirror |
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.json 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
Lissy93/CV is licensed under MIT © Alicia Sykes 2025.
For information, see TLDR Legal > MIT
Expand License
The MIT License (MIT)
Copyright (c) Alicia Sykes <alicia@omg.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.
© Alicia Sykes 2025
Licensed under MIT
Thanks for visiting :)
