The problem: The auto-generated table of contents in Help Center articles renders every entry identically — one font, one size, one color, no indentation. H1 and H2 headings appear as a flat list, so readers can't see the structure of the article at a glance. In long articles (exactly where a table of contents matters most), a flat list of a dozen identical entries is hard to scan and defeats the purpose of having a TOC.
The request: Add visual hierarchy to the table of contents so heading levels are distinguishable. The standard treatment would be some combination of:
1. Indentation — nest H2 entries under their parent H1, the way most documentation sites do.
2. Size and weight — e.g., H1 entries in bold 16pt, H2 entries in regular 14pt.
3. Color — e.g., H1 entries in the primary text color, H2 entries in a secondary gray.
(Example attached showing the kind of differentiation we mean.)
Even just automatic indentation by heading level — with no configuration options at all — would solve most of the problem. Configurable styles per level would be the ideal version.
This applies wherever the TOC renders: both the Help Center on the web and in the Messenger. Since the TOC is already generated automatically from H1/H2 headings, the structural information exists — it just isn't reflected visually.
The payoff: readers can see article structure instantly, jump to the right section faster, and self-serve more successfully on long articles. Thanks for considering!
