Why publish your CV from the command line?
Most CV builders use the same workflow: log in, fill out forms in a web interface, save your changes. It's straightforward enough, but it adds friction every time you need to update your CV.
When you add a new project, change a job title, or update your skills, you have to navigate back to that web interface and find the right fields. For developers, this creates a disconnect. Your CV lives in one place, your code lives somewhere else, and there's no way to tie them together.
Traditional CV builders also force you into their interface. If you want to switch providers or use multiple formats, you're starting from scratch again.
txtcv: CVs in Git
txtcv brings CV publishing into your development workflow. Store your CV as a JSON Resume Schema file in your repository, then publish updates from anywhere, your terminal, GitHub Actions, GitLab CI, or any server.
Key benefits:
- Track every change in Git: Every CV update gets a commit. Need to revert a change? Restore an old version with Git.
- One command to publish: Update your JSON file, commit, and run
txtcv publish --id <cv-id> cv.jsonto publish. That's it. - Automate your CV: Set up GitHub Actions or GitLab CI to publish automatically whenever you push changes. No manual steps needed. Let computers do the work.
- Works with JSON Resume Schema: Use an open standard format that any tool can read. Your CV isn't locked into one platform.
- Same tools you already use: If you use Git, you can use txtcv. No new interfaces to learn.