Update prism to v1.21.0

[XhmikosR]

Preview: https://elastic-heyrovsky-9fc9ac.netlify.app/

[XhmikosR]

BTW @bryanbraun have you thought about deploying to the gh-pages branch only on tags or manually? Right now, there's a chance that docs are broken if one does not run npm run build. We can automate this with GitHub Actions easily.

[bryanbraun]

Ooo, getting the minified version is a nice improvement. 😄

[bryanbraun]

BTW @bryanbraun have you thought about deploying to the gh-pages branch only on tags or manually? Right now, there's a chance that docs are broken if one does not run npm run build. We can automate this with GitHub Actions easily.

Yeah the "Copy to docs" setup is a little awkward. I'm inclined to not refine this too much right now, because I suspect that some of it will change after I work on #109 .

One option is to deploy the whole repo to github-pages instead of just the /docs folder. That would allow me to link the JS file directly, so the docs would reference the anchor.js on master. I did something like that for https://github.com/bryanbraun/checkboxland.

Github Actions is pretty nice too, though, so lots of options. 😄

[XhmikosR]

I think the best approach would be to deploy with GitHub Actions. That way, you can make sure the live site is indeed the latest master code, assuming you want that and not the latest tag (we can go either way). For example, we deploy our blog from the main branch on https://github.com/twbs/blog/blob/main/.github/workflows/ci.yml

Anyway, let me know if you'd like me to submit a PR for this. You will just need to change the deployment options :)

[bryanbraun]

@XhmikosR, thanks for the example with twbs. I'll keep thinking about the deploy thing. I'll create an issue and ping you if I feel like it's time to go in that direction. 👍