The test page
I don’t currently have any many automated checks on this website. Not something I’m boasting aboutbut a reality I’m willing to accept. I wanted to get up and running quickly when I started and I haven’t incurred any interest on the debt so I leave it.
For now I perform an unscripted manual check quite naturally: I look at the live site after I’ve made changes to it. On this page I have one example of each features the website has – metadata, an image and an after thought, one of each of my MDX components, rich markdown and code snippets.
Process
- Add a new feature to the site
- Include an example of it here
- Periodically check everything on this page is working
Issues
⚠️ Would I notice if I added new feature and forgot to include it here?
Well it’s 2026 now so I can add a note so agents don’t forget. 🤖⚠️ Would I notice if any of them broke?
Probably not, at least not straigth away but it hasn’t been a problem yet
Features of this site so far
JSX and Markdown
I’m not checking on this, it’s a feature of gatsby-plugin-mdx
Edit (2026): I migrated to Astro and it’s cool to see how easily it’s all still working
However, shortcodes are the JSX components that I pass in to MDXProvider and my automated checks wouldn’t tell me if they were missing
Expected shortcodes
BlockQuote
Example of citation URL without a pathname
dc5b.com –DC5B is going on behind the scenes
WebGL model view projection
developer.mozilla.org [...] WebGL_model_view_projectionThis article explores how to take data within a WebGL project, and project it into the proper spaces to display it on the screen. It assumes a knowledge of basic matrix math using translation, scale, and rotation matrices. It explains the three core matrices that are typically used when composing a 3D scene: the model, view and projection matrices.
Emoji
<Emoji label="positive checkmark">✅</Emoji>✅ My Emoji component adds accessibility attributes around an emoji
Link
The Gatsby <Link> is available to all MDX layouts
Frontmatter
Optional data about a Note page.
| Key | Use |
|---|---|
afterthoughts | end of note page |
date | sort of notes index |
description | metadata descriptions |
image | displayed at top of note page |
image | referenced in metadata image |
imageAlt | alt text for image (above) |
title | listed in notes index |
title | metadata titles for note page |
title | top of note page |
title | window title for note page |
private | true or false |
Footnotes
I don’t have “many” automated checks
Initially I wrote that I don’t have “any” automated checks, then I started to notice automated checks that I had ignored:
-
Linting happens whenever I save assuming the format of the document is correct. If it fails I notice! This is a frequent, super cheap check that is very easy to keep green.
-
Deployment and build checks are another frequent, unobtrusive check that should not be underrated. When I push to
mainI get emailed if a build fails and I notice if deployments are behind.