ewpt3ch/resume
1
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

added "make it your own" instructions to README.md

Browse Source
This commit is contained in:
Eric Phillips
2026-02-09 14:11:13 -07:00
parent 5b8e5bba69
commit a3d0b71b39
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9 -2
View File
@@ -5,12 +5,19 @@ Resume [![status-badge](https://woodpecker.ewpt3ch.dev/api/badges/2/status.svg)]
### TODO ### TODO
- ~limit rebuild to changes in markdown folder~ - ~limit rebuild to changes in markdown folder~
- get resume.html with all relevant info ~ - get resume.html with all relevant info ~
- create link to download pdf ~ - create 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. - create sub resumes for different roles(dev, data science, sysops) with links to the relevant html and pdf for specific job applications.
### How it works
Resume(s) are written in [markdown](https://www.markdownguide.org/) and stored in the markdown/ folder. When the project is pushed and has changes: Resume(s) are written in [markdown](https://www.markdownguide.org/) and stored in the markdown/ folder. When the project is pushed and has changes:
- in the markdown folder - in the markdown folder
- the src folder - the src folder
- or the message [ALL] is in a commit - or the message [ALL] is in a commit
it outputs html and pdf files that get published at www.ewpt3ch.dev/resume. it outputs html and pdf files that get published at www.ewpt3ch.dev/resume.
### How to use it yourself
- 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.