You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
grunt-jsdox can generate a TOC of the files that make up an API, but within a file, you're left to manually navigating through headings. A per-file ToC would be great.
The text was updated successfully, but these errors were encountered:
That's a bit over my head, but should a ToC not be standard with all generated documentation of significant length? The UX for navigating, say, http://nodejs.org/api/http.html, would be far worse without a ToC.
Whether the base templates should include a ToC or not hasn't come up yet, so perhaps this wasn't very high on people's list. For larger files, I could see this to be useful, so we'll keep this one open in case someone has something they'd like to contribute. And if not, someone might take it on.
grunt-jsdox can generate a TOC of the files that make up an API, but within a file, you're left to manually navigating through headings. A per-file ToC would be great.
The text was updated successfully, but these errors were encountered: