+1 for this. Would love native support without needing hacky workarounds
+1 for this feature!
+1 for showing tags in published pages.
Yes, this was bit disappointment for me. This is such a āmust-beā that without it, publishing is much less useful. I currently need to duplicate all the properties in a table - productivity nonsense.
Without this feature it does not make publishing subscription worth keeping I am afraid.
Use case or problem
Frontmatter / Properties is a key mechanism for navigating my vault. The inability to āObsidian Publishā the Properties of a Note impedes navigation of the published vault contents.
Before the release of Properties in Obsidian, I had baked this into my Templates
Primary Categories: [[01 - Recipes]]
Secondary Categories: { Add link(s) back to related SECONDARY categories }
Tags and Links: #recipe { Add additional relevant tags and links }
Which rendered consistently between both the App and the Published result:
I later adopted the (preferable) Properties functionality. Notes now look likes this in the app:
Yet lose all functional navigation once Published:
Proposed solution
A mechanism to Publish n > 0 Properties
- (Nice to Have) a function to exclude certain properties (e.g. tags) from publication
Current workaround
My only known-functional work arounds are to abandon the use of Frontmatter / Properties OR abandon Obsidian Publish in favor of a custom Hugo (or similar) workflow. Neither workarounds are desirable.
Related feature requests
@Cacapon Shared a similar desire in Help - I want to enable links written in properties in Obdisian Publish
thank you very much!
I assume I add the CSS Snippet in the publish.css
Where do I add the .js file?
+1 for a native solution. I finally got the first code example for showing the created date to work with some modifications (has to be exact to my property name and not have other properties listed that I donāt have ā my notes donāt have āupdatedā property).
Also even with the code working, I seem to have to refresh each page individually for the date to show.
1 Like
Is it possible to check if the team is even considering something like this?
1 Like
I saw on Discord that Dynamic Views (which will use properties) will support Publish, which should mean some way to show said properties will also be included.
4 Likes
Use case or problem
Obsidian Publish doesnāt respect frontmatter (note properties) fields. They are not displayed or used for link navigation once the vault is published online.
I am trying to use existing notes properties (which represent relationships between notes, tags etc) to replicate the same structure as my local vault in the published version, but Obsidian Publish ignores note properties thus breaking links.
Iād also like the tags to be displayed and navigatable just like they are in the app.
Proposed solution
Make Obsidian Publish display note properties (could be toggle-able for those that donāt want that).
Make Obsidian Publish understand the links in note properties and use them to present relationships between notes (currently only in-line links are respected).
Current workaround (optional)
There are some hacks Iāve seen in the forum but nothing seems to work well enough to be an accepted solution.
Related feature requests (optional)
3 Likes
Use case or problem
I use frontmatter properties to store links to other notes. For example:
---
tags:
- note
about:
- "[[Software testing]]"
- "[[Quality assurance]]"
- "[[Professional development]]"
- "[[Continuous learning]]"
- "[[Community engagement]]"
- "[[Test automation]]"
publish: "true"
---
When publishing, these links are ignored. The published note does not display the about property, nor are those links included in the graph view. Tags are also hidden.
This creates a gap between my internal note structure and the published content. It forces me to either duplicate information into the note body or lose semantic connections in Publish.
Proposed solution
Add a configuration option in Publish settings to show or hide frontmatter properties.
- Allow per-property control (for example, hide
publish, but displaytagsorabout). - Render wiki-style links from frontmatter as working links in the published note.
- Ensure that these links are also visible in the published graph view.
This would keep frontmatter useful for metadata and relationships, without having to duplicate them into the note body.
Current workaround (optional)
The only workaround is to move properties like about and tags into the body of the note. This breaks the semantic use of frontmatter and clutters the note with metadata.
+1 so surprised this isnāt already implemented- and dissapointed! My tags, backlinks, and epistemic status all live in the metadata of my notes. Unsure how to make this information easily available on my published site without totally jumbling my workflow
1 Like
+1 I really want this feature. my vault navigation heavily relies on properties and Iām sad they donāt work natively with publish.