Jeremy Monat

[Sphinx failed](https://github.com/sympy/sympy/runs/7828985899?check_suite_focus=true#step:6:813): ``` The docs build failed with the following errors: /home/runner/work/sympy/sympy/doc/src/explanation/solve_output.rst:125: WARNING: py:func reference target not found: Equality ``` The cited line contains ``:func:`~.Equality` ``. I believe the problem...

As it happens, SymPy's [documentation](https://docs.sympy.org/dev/contributing/docstring.html#cross-referencing) has this exact example (the backticks may not appear correctly below, so recommend you copy from that page): ``:obj:`~sympy.core.basic.Basic.subs``` where `:obj:` can refer to any...

### Tangential question about MyST auto-generated targets Instead of adding a custom target to a documentation file, I discovered that [MyST auto-creates targets based on headings](https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#auto-generated-header-anchors) for pages written in...

This [solving guidance page](https://output.circle-artifacts.com/output/job/d610c21e-fcc9-4f9f-9fc6-171148d2204e/artifacts/0/doc/_build/html/guides/solving/solving-guidance.html) is ready for final review, or merging if there are no more comments. Other solving pull requests (additional pages such as #23802) will link to this...

> > Tangential question about MyST auto-generated targets > > Instead of adding a custom target to a documentation file, I discovered that [MyST auto-creates targets based on headings](https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#auto-generated-header-anchors) for...

Seems good. Suggest having a section on doctests, both writing and running them. That's relevant to both code (should have examples as doctests in docstrings) and documentation (often want to...

Actually, suggest making Contributing Guide general to any type of contributing (code or documentation) by moving - Code Conventions - Running the Tests into a new, subsequent section called Contributing...

Good news: the [Executable Books community will try to solve the accessibility issue](https://github.com/executablebooks/sphinx-design/issues/78). I was trying to build the docs with cards to verify that manually applying an [accessibility solution...

Hmm, Lighthouse is still finding the [accessibility issue Links do not have a discernible name](https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Foutput.circle-artifacts.com%2Foutput%2Fjob%2Ff6ec52b3-ccb3-474d-bbb2-2aaf579d1822%2Fartifacts%2F0%2Fdoc%2F_build%2Fhtml%2Findex.html&strategy=desktop&category=performance&category=accessibility&category=best-practices&category=seo&category=pwa&utm_source=lh-chrome-ext). I noticed the [PR was merged today in ExecutableBooks](https://github.com/executablebooks/sphinx-design/pull/89); it doesn't seem like they've out...

[sphinx-design put out a release with this fix](https://github.com/executablebooks/sphinx-design/releases/tag/v0.3.0). @asmeurer can you rebuild the docs preview on this PR, then we can check if the cards accessibility issue is fixed?