Yes, I agree, buttons in the Markdown files would be useful.
We’ve been adding these buttons directly to the notebook file so they’re visible wherever the notebook is rendered: Colab, GitHub, website, or unrelated projects that aggregate notebooks. Could do something similiar for Markdown files. This is probably easiest and can be enforced in CI tests (GitHub Actions) using nblint or another check.
We can also think about auto-adding buttons in the docs pipeline when published to the website. Would be nice to standardize this across the site but requires docs infra work and not sure if we’d gain much over CI tests.