Please select if your request is either something new or an enhancement
[x] Enhancement of an existing Feature.
[ ] Request of a new feature.
Please select the area your request applies to. (Multiple selections are possible)
[ ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[x] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)
Is your feature request related to a problem? Please describe
When part of a vault is meant to be a blog hierarchy, the rendering in the published site doesn't include common blog information:
Date published
Author
etc.
When it comes to blog guidance, I have looked at the Dendron wiki at Blogging (dendron.topic.publish-legacy.blogging). Though, because it is within a *.publish-legacy.* hierarchy, I do not know whether this has been deprecated and replaced with something else in the newer NextJS publishing approach.
Describe the solution you'd like
It would be great to support some, or all of, the following:
Date published (which would use the date field in Dendron frontmatter)
Estimated read time (this looks to be generated by something like a (word count * ?) = (read time))
Author (using the author field in Dendron frontmatter)
A small author section looks like it could probably be rendered from a user.<name> profile: name, social media, etc.
A user.<name> profile could then act like tagging does, in a way, by showing all blog posts done by an author
Describe alternatives you've considered
When it comes to adding additional author information, that could also be done by extending the Dendron frontmatter to have nested values, like image currently has, instead of having it reference information found in something of a user.* or author.* note. This path for authorship, though, has less discoverability potential around what the same author has made, no extended about/profile page for an author, etc.
Additional context
Example author and article metadata info is seen rendered toward the top of these pages, except for Dendron: est. reading time, author name, publish date, social media of author, etc.
Please select if your request is either something new or an enhancement
Please select the area your request applies to. (Multiple selections are possible)
Is your feature request related to a problem? Please describe
When part of a vault is meant to be a blog hierarchy, the rendering in the published site doesn't include common blog information:
When it comes to blog guidance, I have looked at the Dendron wiki at Blogging (dendron.topic.publish-legacy.blogging). Though, because it is within a
*.publish-legacy.*
hierarchy, I do not know whether this has been deprecated and replaced with something else in the newer NextJS publishing approach.Describe the solution you'd like
It would be great to support some, or all of, the following:
date
field in Dendron frontmatter)(word count * ?) = (read time)
)author
field in Dendron frontmatter)user.<name>
profile: name, social media, etc.user.<name>
profile could then act like tagging does, in a way, by showing all blog posts done by an authorDescribe alternatives you've considered
When it comes to adding additional author information, that could also be done by extending the Dendron frontmatter to have nested values, like
image
currently has, instead of having it reference information found in something of auser.*
orauthor.*
note. This path for authorship, though, has less discoverability potential around what the same author has made, no extended about/profile page for an author, etc.Additional context
Example author and article metadata info is seen rendered toward the top of these pages, except for Dendron: est. reading time, author name, publish date, social media of author, etc.
dev.to
republish example: Best Mobile Note-Taking Apps for Markdown