Spurious section headers in custom categories

[reitzig]

I collect symbols in custom categories. Despite the fact that they are all public, I get "Public" headers in the index list.

Exhibit A:

Exhibit B:

I also note that entries have different distances between them, which just looks odd.

[reitzig]

Ah, my bad; these are // MARK: comments in our code. But why on earth are they included in these indices? They are far away from the declarations they accompany here in the index, and are used to organize files, not documentation categories.

I think MARKs should be dropped from indices of custom categories.

The bigger gaps coincide with the beginnings of new files. That also makes little sense in custom categories: symbols may share a file but not the documentation category, or vice versa.

[johnfairh]

Continuing down the 'css kludges' path, these 'mark:' derived lines are in a div styled "task-name-container" so can be hidden like the others.

[reitzig]

Alas, it does not seem possible to distinguish site types. I want the MARKs in class views (they make sense there). I only want to hide them in custom categories where you get a really weird mix; note how arbitrary the task-group divs are (if you mix symbols from different files and/or order them differently than in the files)!

[johnfairh]

Splice in <style>.task-name-container {display: none;}</style> just before </head> of the pages you care about? (yuck! I'm done now.)

[reitzig]

I won't consider manual approaches; any workaround needs to be scripted. Since I don't see a way to identify indices of custom-category section pages, this won't work. :/ Thanks, anyway.

[johnfairh]

I noticed Siesta uses custom categories + strategically placed MARK comments to good effect. An enhancement here then could be to drop the auto MARK and add the ability to add section headers instead via the config file.