Push consistent outputs into recurring workflows
Not just export once, but make export and distribution part of a repeatable operating flow.
Workflow Publisher
A future layer for moving Obsidian outputs into downstream tools and channels.
A future-facing direction for turning exported assets into repeatable publishing flows across docs, slides, internal updates, and external destinations.
ArtifactsTemplatesAutomation
Why this mattersAn exploration guided by launch signals.
This direction is here because export requests are already pointing beyond a single file type.
Use cases
Built around the moments where notes need to travel further.
Bridge note creation and downstream publishing
Reduce the friction between writing in Obsidian and actually shipping the output somewhere else.
Why this matters to the hub
It turns demand signals into the next product direction.
This concept exists because feedback from real launch traffic is expected to point beyond one plugin and toward a broader export workflow category.
Represents the broader platform opportunity beyond one plugin
Helps test whether export is a feature or a product category
Signals we want to learn from
These questions help decide what the hub should build next.
Do users only want files, or do they want destination-aware workflows?
Which repeated publishing paths are worth productizing?
Next step