Skip to content
forked from adrienrn/resume

Personal resume w/ HackMyResume and a custom fresh-theme

Notifications You must be signed in to change notification settings

laurentzoz/resume

 
 

Repository files navigation

resume

Hosted via Github Pages : https://laurentzoz.github.io/resume/

This is a fork of adrienrn/resume, big thanks to him !

About

A little personal project to author a kick-ass resume in HTML or PDF.

Most of the work is leveraged by hacksalot/HackMyResume, kudos to him.

This project contains my resume as a .json file (FRESH resume) aggremented with tools to help develop and release:

  • Dockerized HackMyResume
  • Custom FRESH theme, called henlo
  • Puppeteer to generate the PDFs -- see below why
  • BrowserSync to serve the HTML/CSS and live reload
  • Gulp to watch files and rebuild, refresh while developing

With a little work, it could become useful as starter-pack/example maybe?

Get started

The first time, you probably just want to start the container.

~$ docker-compose up

There, you're done and go to http://localhost:9000/base.html.

Gulp is watching files and BrowserSync will live reload your page automatically. Any change to .json, .html, .hbs or .css, will trigger a rebuild of both the base.html and base.pdf output files (see dist/ folder). Simple but realy handy while working on your content or design.

Generate

~$  docker-compose run node /bin/bash -c 'yarn run hackmyresume:dist'

This will generate the final files:

  • /dist/resume.html
  • /dist/resume.pdf

Any files named private-*.json in the src/ will be included in this type of build. I use it to have my contact informations private and not committed to this repository.

FAQ

Are you going to release the henlo theme?

🇫🇷 Oui, 🇩🇪 Ja, 🇷🇺 Da!

However, at the moment it only supports a handful of FRESH fields that I am using. 👹

Why use Puppeteer?

Yes, HackMyResume can generate PDF resume. However:

You can find the a script, provision.sh, to install those 3 tools and test them. This should definitely go into the dockerfile but since I do not use them, I didn't include them in the container, yet.

Why all the fuss in the Dockerfile?

I didn't have a Dockerfile before needing Puppeteer, and I was using a default node image.

However the documentation is great (error messages are nice too!) and everything is explained there:

Next steps?

  • Move the theme into its own repository.
  • Create another repository without my data, to offer dockerized and live reload as a "starter pack"; if you would find it useful, open an issue.
  • Make a PR to hacksalot/HackMyResume to include puppeteer support!

About

Personal resume w/ HackMyResume and a custom fresh-theme

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • CSS 36.4%
  • Handlebars 30.9%
  • JavaScript 13.5%
  • Dockerfile 9.2%
  • Shell 8.1%
  • HTML 1.9%