docs: fix Furo TOC error on Django fork page#28
Merged
Conversation
Furo renders its own right-hand page TOC from the section structure; the manual `.. contents::` directive conflicts with it (no other page uses it). Removing it fixes the Furo TOC rendering error.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Removes the manual
.. contents:: :local:directive fromdocs/features/django-fork.rst. Furo renders its own right-hand "On this page" TOC from the section structure, and the manual directive conflicts with it — no other page in the docs uses it. Build succeeds with only the pre-existing_static/favicon warnings.