Display Minutes Listing

[trickeydan]

This PR will display a listing of links to the minutes.

It will auto-update without changing this repo if a webhook is added to rebuild the site on Netlify. A similar suggestion was discussed in #25.

NB: Build is failing due to the spelling check script displaying odd behaviour. It doesn't accept the list as sorted even after the sort.sh is run.

[nmalky]

Now that we have build-online.sh, what is the purpose of build.sh?
If there isn't any, it should be deleted, and all instances of build.sh removed (e.g. README.md hasn't been changed to build-online.sh)

build-online.sh ignores the cache and is thus purposed for rendering the latest version of the site on Netlify / CircleCI. build.sh doesn't ignore the cache and thus builds significantly quicker for development purposes.

[RealOrangeOne]

Why do we need the minutes baked into the site? Surely linking to the repo is enough? This means that the site has to be re-deployed every week so the list updates, even if nothing has changed. Just linking is a far nicer solution!

[trickeydan]

I would argue that this makes the minutes more accessible to people unfamiliar with GitHub. If the webhook is called when new content is pushed to the minutes repo, then it has changed.

Also, as it only takes seconds to re-deploy the website, why would this be a problem?

[RealOrangeOne]

more accessible to people unfamiliar with GitHub

They don't need to know about GitHub, or how it works. Assuming they understand the concept of folders and files, they can traverse the web UI. The web UI is incredibly easy to use, by design! I fail to see how this is any different?

why would this be a problem

Because, it's another build step, and another way to get outdated. It's theoretically possible to force the website to redeploy, it's still a hack

[trickeydan]

It's not a hack, it's listed on their docs!