I converted all my notes from Markdown to AsciiDoc. There it works with the tags in comments too. But the tags are only recognized by vscode-nested-tags.
If you could use header attributes or document attributes for tags too, then the content would be visible and usable for "normal" AsciiDoc processors too. And the usage would be clear and simple. This would be the equivalent of YAML headers.
.content of test.vscode-nested-tags.4.adoc
= Test vscode-nested-tags in AsciiDoc
FirstName LastName; SecondFirstName SecondAuthor
//header attribute :keywords: is not supported by vscode-nested-tags
:keywords: @Someday, +home, +work, #hashtag, topic, here/is/a/nested/example, project.task.nested
This is the document.
Tags in comments are supported:
// @nested-tags:topic2,here2/is/a/nested/example
//document attribute :tags: (or whatever) are not supported by vscode-nested-tags
:tags: topic3, here3/is/a/nested/example, project.task.nested
Tags can be extended:
// @nested-tags:topic4,here4/is/a/nested/example
:nested-tags: topic5, here5/is/a/nested/example, project.task.nested
Each document holds a set of name-value pairs called document attributes. These attributes provide a means of configuring the AsciiDoc processor, declaring document metadata, and defining reusable content. This page introduces document attributes and answers some questions about the terminology used when referring to them.
I converted all my notes from Markdown to AsciiDoc. There it works with the tags in comments too. But the tags are only recognized by vscode-nested-tags.
If you could use header attributes or document attributes for tags too, then the content would be visible and usable for "normal" AsciiDoc processors too. And the usage would be clear and simple. This would be the equivalent of YAML headers.
.content of test.vscode-nested-tags.4.adoc
https://docs.asciidoctor.org/asciidoc/latest/document/metadata/#keywords
https://docs.asciidoctor.org/asciidoc/latest/attributes/document-attributes/
:tags:is an example for a document attribut.