limit rebuild to changes in markdown folderget resume.html with all relevant infocreate link to download pdf- create sub resumes for different roles(dev, data science, sysops) with links to the relevant html and pdf for specific job applications.
Resume(s) are written in markdown and stored in the markdown/ folder. When the project is pushed and has changes:
- in the markdown folder
- the src folder
- or the message [ALL] is in a commit it outputs html and pdf files that get published at www.ewpt3ch.dev/resume.
- clone the repo
- replace the content in markdown folder with you own
- replace 'name' in main.py, or import it somehow
- edit .woodpecker.yml or create github actions etc to build and publish at you domain.
- This doesn't have to be exclusively used for a resume, any text document that one wants to store in markdown format, in a revision control system, and published to a website with html and pdf, or without pdf, could use this.