jaimergp

Might need a new exclude in https://github.com/conda-forge/conda-forge.github.io/blob/8335651ca036b1d883d994cae118b4d4d1161c6b/.github/workflows/deploy.yml#L51-L63 Something like: ``` --exclude '^.*/status/migrations/.*$' ```

The problem is that the migration details URLs are generated dynamically on the JS client, but a static request gives a 404, so they will always fail the checker.

Correct.

Love this. The biggest concern is not breaking any existing URLs and anchors that might refer to existing content. How we have addressed this so far: * If there's a...

I don't think that works in this repo (but you can always close and reopen on your own). I issued a CI rerun, let's see.

Thanks!

Thanks for the excellent feedback. Hopefully we can tackle this as part of https://github.com/conda-forge/conda-forge.github.io/issues/2164. I agree with your points. conda-smithy has some docs in [its README](https://github.com/conda-forge/conda-smithy), but not sure if...

Last year, I experimented with how Diátaxis would apply to our docs in https://cf-infra-docs.netlify.app/docs. Some of the docs written for that experiment are being migrated over to our new website....

cc @jakirkham because I think you brought this up a couple core meetings ago and I said I'd follow up. This is my crude attempt at getting the conversation started.

> Label them as necessary, or add them to a milestone so they are easy to find. Org-wide issue search with labels works pretty ok. We can use the `label:fundable`...