Change Details

Phriction articles can have many headers of different depths. Nested instructions and contents are part of most use cases of Phriction. But the auto generated table of contents is a flat list. If you have three depths of headers, they all seem alike in the ToC. That is a big problem in finding the right spot in a big Phriction article. The usefulness of the ToC is decreasing fast if you have more than 10 headers with 2 or 3 different depths. The ToC should be more structured and clearly arranged. The ToC should be automatically numbered and indented with very new header depth (like the ToC of Wikipedia).

Phriction articles can have many headers of different depths. Nested instructions and contents are part of most use cases of Phriction. But the auto generated table of contents is a flat list. If you have three depths of headers, they all seem alike in the ToC. That is a big problem in finding the right spot in a big Phriction article. The usefulness of the ToC is decreasing fast if you have more than 10 headers with 2 or 3 different depths. The ToC should be more structured and clearly arranged. The ToC should be automatically numbered and indented with every new header depth (like the ToC of Wikipedia).

Phriction articles can have many headers of different depths. Nested instructions and contents are part of most use cases of Phriction. But the auto generated table of contents is a flat list. If you have three depths of headers, they all seem alike in the ToC. That is a big problem in finding the right spot in a big Phriction article. The usefulness of the ToC is decreasing fast if you have more than 10 headers with 2 or 3 different depths. The ToC should be more structured and clearly arranged. The ToC should be automatically numbered and indented with every new header depth (like the ToC of Wikipedia).