Plugin maintenance

[AB1908]

Hi @blacksmithgu, can we document how you've set up the repo so that other collaborators can create releases and update the docs while you're not around? It looks to me like you've set up a tag based GitHub Action but I want to make sure I know what I'm doing before I create a new release for the docs.

[blacksmithgu]

Documentation is done via a GitHub Action here; I think the easiest thing for maintainability will be to add an additional workflow_dispatch trigger so it can be kicked off by contributors (see https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow).

Regular releases use the ./scripts/release and ./scripts/beta-release scripts, which compile, create a GitHub release, and publish to npm. I'll have to see how to allow multiple people to commit to npm, but that is only relevant for API changes (you can comment it out in the very short term and create new releases easily that way).

[blacksmithgu]

Note you can just directly do what the workflow does to update the docs, as well:

pip install mkdocs-material mkdocs-redirects
cd docs
mkdocs gh-deploy --force

[AB1908]

I ran into some error with mkdocs and didn't poke further. I'll check that out again.