Drop the table of contents from the landing page - #543
Draft
zieka wants to merge 1 commit into
Draft
Conversation
The entry point already shows no sidebar; the table of contents beside it listed three headings on a page short enough to scan without one. Uses the front matter flag, the same native mechanism as displayed_sidebar, so the change is scoped to this one document and every other page keeps its TOC. Caps the measure as a consequence. With neither navigation column, nothing constrained the text and it ran to ~160 characters a line, roughly twice a readable measure. 830px is what an article gets on an ordinary doc page, so the landing page reads at the same rhythm as the pages it links to.
zieka
force-pushed
the
fix/landing-page-toc
branch
from
September 3, 2026 18:52
4d2d1e3 to
9ade44c
Compare
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
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.
Problem
/) carries both navigation columns' worth of chrome for a page that needs neither, so the first thing a visitor sees is framing rather than content.Objectives
Assumptions
hide_table_of_contentsis front matter on a single document, so the change cannot reach any other page. Confirmed: exactly one file indocs/carries the flag.displayed_sidebar: nullalready on this document, so both columns are removed the same way rather than one natively and one in CSS.html[data-route='/']and affects nothing else.Changes
(1)docs/introduction.md— addshide_table_of_contents: trueto the front matter, beside the existingdisplayed_sidebar: null.(2)src/css/custom.css— capsarticleat 830px and centres it, under the existinghtml[data-route='/']block.No tests: this repo has no test framework or test files, and the change adds no testable logic.
tscand the production build are the available checks.Notes
data-route, published bysrc/theme/Root.tsx. Docusaurus's owndocs-doc-id-*classes exist only in a production build, so styling one page through them renders differently underyarn start.yarn typecheckclean; production build succeeds; TOC absent on/and present on every other page; article 830px, centred.