This looks fine to me, though it is bringing up that I should look into setting up some sort of CI that builds the documents for us so we can review the final product before merging PRs.

@jbrockmendel Going to merge this when CI passes. I tend to not make branches on the dateutil/dateutil repo because 1. the CI fires on both PR and branch, and I don't know how to get it to not do the same work twice and 2. everyone who forks also picks up all the secondary branches. If you prefer to do it this way that's fine, but nowadays maintainers of the primary repo are authorized to push against PR branches, so one of the advantages of working in the main repo is obviated.

I tend to not make branches on the dateutil/dateutil repo

I'll make a note of it.