This is pretty long but quickly:

• Incremental versions are .1 -- make it 0.1.0.1, 0.1.0.2 if needed and so on. I don't care what (bad) defaults devtools may use. Don't make an extra commit for it but if you're at it for another please change.
• The Tufte URL has to go if it fails. CRAN makes no exceptions here either. Links must work.
• The Travis fail needs to get fixed but I see you are on it.
  More later.

The changes look good in general. I will test later. This is a lovely feature extension.

Stylistic nagging:

• ChangeLog: Please try to use the more concise style I have been employed.
• DESCRIPTION: I am not a fan of Authors@R as I am creator/maintainer here I would like to ask you to revert that to a standard free format list.
• I am not sure I am a fan off the added help files. I might have preferred new/expanded sections in the existing ones. It scatters documentation over many files. But let's leave it as is for now.
• As a general rule, when I contribute to other packages I try not to turn the existing style upside down.

Feel free to harp back if you feel very strongly about any of these points. But as we have the means to code review here, I feel somewhat strongly that it makes packages better if we actually do it.

One other thing: Best way to showcase the use of the new fonts? Screenshots on the README.md? Extra (shorter) vignettes?

• Will change the version on my next commit.
• Fixed Travis: the issue was trusty has Pandoc 1.12.2.1 and current rmarkdown requires >=1.12.3 (https://cran.r-project.org/web/packages/rmarkdown/index.html). I changed travis.yml to usedist: xenial, but an alternative would be toapt-get install a more up-to-date backport under trusty.
• I will address the URL check problem.

I will make the requested style changes in ChangeLog and DESCRIPTION. You're the creator/maintainer and it's right for me to follow your style.

I'll work on making short vignettes to illustrate the new font options.

It should be easy to move the extra help material from separate files to a new section undertintPdf. Very little work, and if that's the way you like to do things, it's easy enough for me to make the change.

Awesome, and sorry for the waterfall. Just got home. Am surprised that Travis bonked now -- I guess I didn't trigger a run sincermarkdown changed to requiring a newer version of pandoc so well done.

R-release checks fine; R-devel just got a local hangup here as my R-devel installation did not haveggplot2 and its tail of depends. Installing those now. But got cleanly to vignettes so did not bite me on the missing URL. win-builder/CRAN would though so we may have to refer it indirectly.

I am on the fence on the where the help should go. No need to rush. Sometimes I like having it in one file. Sometimes I like it being more explicit.

How about if we mix and match? Maybe consider sticking all Rd content into one, but be explicit about the options, choices, effects, ... in another (possibly static with pre-rendered screenshots) vignette?

It's very powerful stuff and folks will want to see the effects so an added vignette would be nice. We can cook that up the next few days.

R-devel checked cleanly here too. Nice work!

I like your thoughts about the vignettes.

The mix and match for the help sounds good. I won't rush on that, but it's easy enough to move the text around.

I can also merge now and did the itty pitty clean up on my side. We'll have follow-up commits anway, eg another PR for another (short) vignette?

Argument in favour of keeping new manual pages (and to maybe look into the section or grouping the others have):

We already had a bunch. Some of them are short but I don't think it matters greatly. Can leave as is.

I'll just merge, do some tinkering here and either commit back later or early tomorrow.

And I made you a collaborator so you have push access too. Still best to mutually review so I'll make my touchups a PR, ok?

Sounds good. It's very nice to collaborate with you.