Kick unused dependencies, rest of docs bits

docs/releasing.md

@@ -26,12 +26,7 @@ If you do not have permissions, the maintainer will set the label on your behalf
 
 ## Changelog
 
-There are two changelogs in the Mithril.js project
-
-- `docs/changelog.md` a hand written curated reflection of changes to the codebase
-- `docs/release.md` an automatically prepended log of changes, managed by pr-release
-
-In future we may collapse these into a single file, the separation is due to the fact the `changelog.md` predates the `release.md` file.
+Currently, `docs/recent-changes.md` holds an automatically prepended log of changes, managed by pr-release. Ideally, I want to get rid of this and just have pr-release somehow push to https://github.com/MithrilJS/docs automatically, but that may take some work.
 
 ## For maintainers
 
@@ -39,28 +34,4 @@ Whenever a new feature branch is opened, a reviewing maintainer should add the c
 
 If a `major` or `minor` feature branch is merged but no labels were set, you can still go back and edit the semver labels.  On label change the release pr will automatically be regenerated and will recalculate the semver version.
 
-## Updating mithril.js.org
-
-Fixes to documentation can land whenever, updates to the site are built and published via `scripts/update-docs.js`.
-
-```bash
-# These steps assume that MithrilJS/mithril.js is a git remote named "mithriljs"
-
-# Ensure your next branch is up to date
-$ git checkout next
-$ git pull mithriljs next
-
-# Splat the docs folder from next onto release
-$ git checkout release
-$ git checkout next -- ./docs
-
-# Manually ensure that no new feature docs were added
-
-$ node scripts/update-docs
-```
-
-After the docs build completes, the updated docs should appear on https://mithril.js.org in a few minutes.
-
-**Note:** When updating the stable version with a release candidate out, ***make sure to update the index + navigation to point to the new stable version!!!***
-
 [pr-release]: https://pr-release.org/