The VS Code Outline is helpful, but it's not part ...
# questions
s
The VS Code Outline is helpful, but it's not part of the content of the note, which would be useful, especially when publishing. I didn't see it as a feature, so I thought I'd ask. I can try to go about solving it another way if not.
s
For publishing, pages will default to generating a local TOC that can be navigated on the right-hand side of a page, like seen on https://wiki.dendron.so/ Though, the right-hand nav doesn't currently indent to differentiate between H1/H2/H3/etc. - we have an issue open here: https://github.com/dendronhq/dendron/issues/1871 Otherwise, Dendron doesn't have a built in TOC keyword to be placed into the plain text files themselves
s
Thanks for the insight and clarity. That's helpful.
Maybe you can help provide some ideas on how I can achieve my goal in Dendron. (If not, no problem.) Here's what I'm trying to do: I have a vault with notes such as test.a, test.b. test.c. The subnotes a, b, and c, each have about about 10-20 sections/subsections. The header for each section is the name of an issue associated with a, b, and c respectively, and the content of each section is the detailed documentation of the issue. The "test" note is to contain a a status summary of the testing being performed, which includes a list of the issues found so far -- essentially, a list of the headers on a, b, and c. Currently, I've resorted to manually "referring" each header of each note into "test" in a list. But, I was hoping to do something like
![[test.a#^TOC]]
to avoid not only the manual entries, but also the upkeep of the links as the work progresses. Can you think of any ways I could lay out my documentation to leverage existing Dendron features to accomplish this better? Thanks for any thoughts or feedback.
( I fully acknowledge that I may be trying to use Dendron for something it is not intended.)
s
Ah, yeah, I don't think Dendron has the ability to do a note reference that is just a TOC of the headers in a different note. You'd have to probably create your own markdown TOC and place it in a header (TOC) and note ref that, like it looks like you may be doing.