3 points | by jamesgill 7 hours ago
4 comments
Interesting, I created two similar projects:
1. markdown resume:
- https://leftium.com/resume
- plain-text version is human-friendly: https://leftium.com/resume?text
- also renders OK on Github: https://github.com/Leftium/leftium.com/blob/main/src/routes/...
- PDF version is produced by printing from browser. (Try Cmd-P)
---
2. invoice generator
- Uses shell scripts instead of make
- Uses weasyprint instead of wkhtmltopdf
Some samples would be nice. Curious how the default output settings look.
Nice. Yours seems to be only for promoting your own resume, right? Mine's a tool for a user to control, customize, and create their own, locally.
Effectively the same. (If your project's resume.md had your details, would it prevent others from using it as a tool?)
Steps for a user to create their own resume (locally):
1. clone repo
2. update the resume.md file
3. run the server locally `npm run dev --open`
4. print from browser (as PDF)
- My version happens to contain a web server that serves the HTML resume (among other pages).
- You can also preview the results in real-time as you edit the MD file.
Compare to steps with your tool:
2. update the resume.md file.
3. run `make`
(I omitted all the setup steps for the sake of comparing the major steps. I suppose if I added a makefile, the steps would be exactly the same.)
Yours is slick. I like it.
Interesting, I created two similar projects:
1. markdown resume:
- https://leftium.com/resume
- plain-text version is human-friendly: https://leftium.com/resume?text
- also renders OK on Github: https://github.com/Leftium/leftium.com/blob/main/src/routes/...
- PDF version is produced by printing from browser. (Try Cmd-P)
---
2. invoice generator
- Uses shell scripts instead of make
- Uses weasyprint instead of wkhtmltopdf
---
Some samples would be nice. Curious how the default output settings look.
Nice. Yours seems to be only for promoting your own resume, right? Mine's a tool for a user to control, customize, and create their own, locally.
Effectively the same. (If your project's resume.md had your details, would it prevent others from using it as a tool?)
Steps for a user to create their own resume (locally):
1. clone repo
2. update the resume.md file
3. run the server locally `npm run dev --open`
4. print from browser (as PDF)
- My version happens to contain a web server that serves the HTML resume (among other pages).
- You can also preview the results in real-time as you edit the MD file.
---
Compare to steps with your tool:
1. clone repo
2. update the resume.md file.
3. run `make`
(I omitted all the setup steps for the sake of comparing the major steps. I suppose if I added a makefile, the steps would be exactly the same.)
Yours is slick. I like it.