Add additional functionality to docs

[ThomasLaPiana]

Closes #260

Code Changes

• add a github link
• add an "edit this page" link
• add an "update at" section

Steps to Confirm

• run the docs locally, test the new buttons

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation Updated

Description Of Changes

Footer functionality is currently overwritten by our theme, but mkdocs supports all of the functionality we want without needing to add it explicitly to the footer. Here is a list of the changes:

• Top-right corner now has a link to our GitHub repository and also shows release version, stars and forks
• there is now a pencil icon at the top of every page that links directly to that page on github for easier editing
• The bottom of every page now has a Last update: December 2, 2021 style footer that shows the last time the file was updated according to git. This is turned off when running locally because no git information exists, but when built for prod this will be included.

[PSalant726]

I haven't had a chance to dig into it, but do you think there are any possible workarounds to override the theme's override of the footer? I ask because the pencil icon is a nice feature, but it only partially achieves what we want. It's fairly easy to miss, and what we're really looking for is an obvious call-to-action that makes it dead simple for readers to contribute.

If not, there's nothing blocking this for me.

[ThomasLaPiana]

I haven't had a chance to dig into it, but do you think there are any possible workarounds to override the theme's override of the footer? I ask because the pencil icon is a nice feature, but it only partially achieves what we want. It's fairly easy to miss, and what we're really looking for is an obvious call-to-action that makes it dead simple for readers to contribute.

If not, there's nothing blocking this for me.

I feel your pain on this one, but we're deep into custom CSS and I don't want to override that for this one change. I agree its not optimal though, and will keep this in mind if we end up doing some CSS refactoring in the future