Remove manual Table of Contents in favor of autogenerated Page Table of Contents #1180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a better fix for the problem described in #1179.
@woodsp-ibm and I realized that it's redundant for us to have a manual Table of Contents section in the docs. qiskit_sphinx_theme will already auto-generate a page table of contents. It's duplicative to have our own manual section too.
We suspect that we picked up this habit from old docs that did it before qiskit_sphinx_theme used Pytorch to autogenerate the page table of contents. It's now an out-of-date practice that has a bad user experience & results in the issue in #1179.