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
The [[toc]] is great, with the one exception that it only covers the document that its called within - which is a little self-defeating as vitepress is already creating a content navigation lookup of the active document on the right-hand side.
We have a getting-started.md that contains a Table Of Contents that needs to reach and detail other markdown files content that reside within the same sub-folder as the getting-started.md - the only way I've been able to gear such a lengthy Table Of Contents is by building manually as the last md authoring step before building for prod - which works, but is time consuming to build and becomes out-of-sync the moment any of the document headings are revised without also patching the manual ToC.
Here's an example of the above, where 1 is the getting-started.md file and other content that's below the ToC, and 2 is another MD file, and then ... so on and so on.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The [[toc]] is great, with the one exception that it only covers the document that its called within - which is a little self-defeating as vitepress is already creating a content navigation lookup of the active document on the right-hand side.
We have a getting-started.md that contains a Table Of Contents that needs to reach and detail other markdown files content that reside within the same sub-folder as the getting-started.md - the only way I've been able to gear such a lengthy Table Of Contents is by building manually as the last md authoring step before building for prod - which works, but is time consuming to build and becomes out-of-sync the moment any of the document headings are revised without also patching the manual ToC.
Here's an example of the above, where 1 is the getting-started.md file and other content that's below the ToC, and 2 is another MD file, and then ... so on and so on.
`md
Getting Started
1.1. Greetings
1.2. Objectives
1.3. Extent
1.4. Listeners
System Synopsis
2.1 Framework
2.2 Intention
...
`
Keen to read any suggestions on how a multi-page reaching ToC could be part of the build process.
Beta Was this translation helpful? Give feedback.
All reactions