One public home for current and future Obsidian tools
Stage 1: Launchable MVP
One shared home for Obsidian tools that deserve real users.
This hub is where plugin launches stop scattering across random links and start becoming a reusable traffic, analytics, and feedback system.
Current focusLaunch, measure, learn
Start with one plugin page, one shared funnel, and one clean feedback path.
Infrastructure already readyPages + Umami
The frontend can move quickly because the analytics backbone is already self-hosted and live.
Why this hub exists
It is not just a homepage. It is the beginning of a launch loop.
A shared growth surface instead of launching every plugin into a different destination
A clean bridge from community discovery to GitHub, releases, and structured feedback
Current plugin
Start with one plugin that already solves a real workflow pain.
Table Exporter
Export rendered Markdown tables to PNG, CSV, Excel, and PDF.
Built for the awkward moment when a table looks right in Obsidian but still takes too much manual work to share, print, or keep moving through the rest of a workflow.
PNGCSVExcel (.xlsx)PDF
Explore the pluginThree-stage rollout
The hub is designed to grow in layers, not all at once.
Stage 1
Launchable MVPThe current focus: one strong plugin page, one shared hub homepage, and one clean feedback path.
Stage 2
Closed-loop growthRicher CTA behavior, cleaner plugin-aware feedback, and a stronger learning loop after launch.
Stage 3
Multi-plugin platformA reusable structure for future plugins and a clearer path toward a broader export workflow category.
Closed loop
The value is in what we learn after the click.
Forum posts, Reddit threads, and chat shares no longer drop users straight into a code repository.
We can compare who clicks GitHub, who prefers releases, and who opens the feedback path.
The strongest repeated requests start pointing beyond one plugin and toward a broader export workflow category.
Exploring next
The hub can already point beyond one plugin.
Section Exporter
Turn note sections and structured blocks into clean shareable assets.
An exploration of exporting callouts, note sections, and structured chunks that are larger than tables but still need to travel into docs, reports, and chats.
PNGHTMLPDF
Explore the directionWorkflow 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
Explore the direction