feat: add plugin marketplace

3 files changed, 44 insertions, 30 deletions

diff --git a/website/src/content/releases/v0-6-3.md b/website/src/content/blog/herdr-0-6-3.md
index 23514cc6..97bd2b28 100644
--- a/website/src/content/releases/v0-6-3.md
+++ b/website/src/content/blog/herdr-0-6-3.md
@@ -1,9 +1,8 @@
 ---
-title: "session persistence, safer updates, and workspace navigation"
-version: "0.6.3"
-path: "0.6.3/session-persistence-safer-updates-and-workspace-navigation"
+title: "Herdr 0.6.3: session persistence, safer updates, and workspace navigation"
 description: "This one adds new persistence paths for updates, server restarts, and larger sessions."
 date: 2026-05-27
+draft: false
 ---
 
 ## Persistence for the hard parts
diff --git a/website/src/content/docs/marketplace.mdx b/website/src/content/docs/marketplace.mdx
index f07b8f87..09a27b2d 100644
--- a/website/src/content/docs/marketplace.mdx
+++ b/website/src/content/docs/marketplace.mdx
@@ -1,39 +1,53 @@
 ---
 title: Marketplace
-description: Publish and share Herdr plugins, and get listed when the marketplace launches.
+description: Discover community Herdr plugins on GitHub, and get your own plugin listed.
 ---
 
-The Herdr plugin marketplace is a discoverable index of installable plugins. It
-is not live yet. This page is how to be ready for it.
+The Herdr plugin marketplace is a discoverable index of community plugins.
+Browse it at [herdr.dev/plugins](/plugins/). It is an automatic index of public
+GitHub repositories, not a reviewed catalog.
 
-## Share a plugin today
+## Browse plugins
+
+The [marketplace](/plugins/) lists every public repository tagged with the
+GitHub topic `herdr-plugin`. Search by name, owner, description, or language,
+and sort by popularity, recent activity, or newest. Each listing links straight
+to its source repository on GitHub.
+
+Discovery is automatic and unreviewed. A listing means a repository tagged
+itself, not that Herdr vetted it, so the
+[trust guidance](/docs/plugins/#trust-and-security) applies before you install
+anything.
+
+## Install a plugin
 
 The marketplace adds discovery on top of installation; it does not replace it.
-Anyone can already install your plugin straight from GitHub:
+Install any plugin straight from GitHub:
 
 ```bash
 herdr plugin install owner/repo[/subdir...]
 ```
 
 Publish a normal public GitHub repository with a `herdr-plugin.toml` manifest at
-its root, or in a subdirectory, and that command works now. See
+its root, or in a subdirectory, and that command works. See
 [Plugins](/docs/plugins/) for the manifest and authoring reference.
 
-## Get listed when it launches
+## Get your plugin listed
 
-If you want your plugin to appear in the website marketplace when discovery
-launches, add the GitHub topic `herdr-plugin` to your repository now. That
-topic is the signal the future index will use for discovery, so tagging a
-public plugin today means it can be listed when the marketplace goes live.
+Add the GitHub topic `herdr-plugin` to a public repository. That topic is the
+only signal the index uses, so tagging a public plugin is all it takes. The
+index refreshes automatically every 30 minutes, so a newly tagged repository
+shows up shortly after, and one that drops the topic disappears on the next
+refresh.
 
-## What a listing will show
+## What a listing shows
 
-A marketplace card will surface your plugin's `id`, `name`, `description`,
-declared `platforms`, and a link back to the source repository. Getting that
-manifest metadata right today is what makes your listing accurate later. Declare
-`platforms` honestly, because the index will use it to show where a plugin runs.
+Each card shows GitHub repository metadata: the repository name and owner, its
+description, star count, primary language, and the time it was last pushed, with
+a link back to the source. The index reads this from GitHub's repository search,
+so keeping your repository description and topics accurate is what makes your
+listing useful.
 
-Plugins stay ordinary GitHub repositories. The marketplace is a discovery layer
-on top of the same `herdr plugin install` path you can use now. A listing makes a
-plugin easier to find; it does not mean Herdr has reviewed it, so the
-[trust guidance](/docs/plugins/#trust-and-security) still applies.
+The index does not parse `herdr-plugin.toml` yet, so manifest fields like the
+plugin `id`, declared `platforms`, and `min_herdr_version` are not shown in v1.
+Forks and archived repositories are excluded from the list.
diff --git a/website/src/content/docs/plugins.mdx b/website/src/content/docs/plugins.mdx
index 9f069fdf..9f57ff47 100644
--- a/website/src/content/docs/plugins.mdx
+++ b/website/src/content/docs/plugins.mdx
@@ -304,10 +304,11 @@ state should own their files or database.
 
 ## Marketplace
 
-A plugin marketplace is coming. Plugins are already shareable today: publish a
-GitHub repository with `herdr-plugin.toml`, then share
-`herdr plugin install owner/repo[/subdir]`.
-
-If you want the plugin to appear in the website marketplace when discovery
-launches, add the GitHub topic `herdr-plugin` to the repository now. See
-[Marketplace](/docs/marketplace/) for how publishing and discovery will work.
+Community plugins are discoverable in the [marketplace](/plugins/), an automatic
+index of public GitHub repositories tagged with the topic `herdr-plugin`.
+Plugins stay ordinary GitHub repositories: publish one with `herdr-plugin.toml`,
+then share `herdr plugin install owner/repo[/subdir]`.
+
+To get a plugin listed, add the GitHub topic `herdr-plugin` to its public
+repository. The index refreshes every 30 minutes. See
+[Marketplace](/docs/marketplace/) for how discovery works.