We already have a path forward on the next iteration of Phriction, and it doesn't include this direction. Please read Contributing Feature Requests and Describing Root Problems if you have future feature suggestions, root problems are required for any request filed. Thanks!

It does include this direction (T9868), so I'm looking forward to this.

The root problem is clear: The ToC is useless in a highly hierarchical Phriction article with many nested headers.

We don't consider that to a be a root problem.

The ToC is a currently a bandaid to a design problem, that people put too much information into a single page due to lack of alternative choices. Our solution moving forward isn't to just improve the ToC, but to improve Phriction overall and allow more CMS level customization (like a permanent sidenav). Knowing why so much information is placed on a page is the root problem we're looking for. If we just improve the ToC, I don't feel we're solved the root problem.

You may be right, that the root problem is people putting to much content in Phriction articles. But even a need content seperation like this one

Installation

Step 1

Step 2

Setup

Step 1

Step 2

would greatly improve with a structured ToC like that

1. Installation
  1.1 Step 1
  1.2 Step 2
2. Setup
  2.1 Step 1
  2.2 Step 2

But looking forward to your solutions!