Small changes before Saturday

[ismayc]

This will serve as future release checklist as well.

• Just this time: get package list consistent
• Check for broken @ and ?? references
• Ensure Chapter/Section/Subsection consistency. Ex: 3/3.1/3.1.2
• Hide all Learning Check solutions
• Take banner off of master branch docs deploy after we create a dev branch.
• Make changes in index.Rmd to update versions of development and released.
• Tag release on GitHub for new released version.
• Update past versions list in Section 1.4. See Fix links to previous versions in Section 1.4 #23 and After release, lock master branch; do all editing in dev branch #31
• Change travis to look for changes on the dev branch and then publish to gh-pages (for Albert's class on Monday).
• Create a referral page from https://github.com/ismayc/moderndiver-book to https://github.com/moderndive/moderndive_book (Contents in the old repo should be removed prior to the next major release--likely this summer.)
• Change links to script files to be to https://moderndive.com/scripts/ for the released version of the book. Not that big of a deal but it would be confusing if we changed some of the code in the development version of the book and then someone was trying to run the ModernDive.com code instead. We should probably set a toggle for this. (Delayed until next release.)

[rudeboybert]

Hey @ismayc I'm done all my TODO's on this list from back in January and copied over all elements to the "release checklist" in the Google Doc, so I removed myself from assignees.

[ismayc]

@rudeboybert I finally copied over your slick trick to get https://ismayc.github.io/moderndiver-book/ to route to https://www.moderndive.com. Nice work!

[rudeboybert]

It's a hack, but it gets the job done. #DoneIsBetterThanPerfect