Use something like html-pdf to generate PDFs from the command line instead of having to use the print dialog every time.

Currently, every work/education experience is being outputted. They're all the default page. I'll need to do so after Metalsmith build since I need the source files metadata & contents.

would be a very helpful enhancement

{ TypeError: /Users/phivk/Documents/_Work/_CV/_2017/metalsmith-resume/templates/components/experience.pug:6
    4|   +section
    5|     //- Position
  > 6|     h3.f3.mb2.mb0-p.fw6= exp.title
    7|     //- Metadata
    8|     +left-column
    9|       ul.list.ml0.pl0.f5.mt1.fw2

Cannot read property 'title' of undefined
    at block (eval at wrap (/Users/phivk/Documents/_Work/_CV/_2017/metalsmith-resume/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:128:60)

it would be nice if the variable set in site.yaml would specify max_jobs and would still render the present experience md files when there are less files than the maximum.

same story for schools / education md files...

PFA the debug.log file
Are there any dependencies to install?

When I remove all proficiencies (as suggested in person.yaml), like such

proficiencies:
  # - list item

the build process throws a throws a TypeError, which prevents the resume being built:

{ TypeError: metalsmith-resume/templates/default.pug:32
    30|               +experience(collections.education[i])
    31| 
  > 32|         if person.proficiencies.length > 0
    33|           +section
    34|             +left-column
    35|               +section-title('Proficiencies')

Cannot read property 'length' of null
    at eval (eval at wrap (metalsmith-resume/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:526:25)

I'm on OSX 10.12.6 using latest node (5.5.1)

Would be great if you could pull all your info in from LinkedIn.

set up exactly like my other sites?

¯_(ツ)_/¯

Would allow uncss & cssnano to run only when environment is set to prod, speeding up local development considerably.

I would like the ability to adjust my resume to different potential employers. I want to keep job descriptions available in their md files, but have the ability to exclude them easily from the current build.

this could be easily done through a YAML metadata field, e.g. published: false and then list jobs / schools in their respective templates unless published is set to false
Idea would be that by default published is considered true, so it wouldn't break existing functionality.

Looks like I was a big dumb-dumb and messed up when I did a5c5330

The defaultValues and drafts were working in harmony to remove all that cruft from the generated site. I just forgot that's why they were there.