You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Use that command to fix deprecated class syntax across the repo instead of doing large manual replacements.
25
+
26
+
## Adding A Plugin To The Website
27
+
28
+
- Add the plugin registry entry in `apps/web/src/config/plugins.ts` inside `actionDefinitionRows` with the package name, title, short description, and GitHub URL.
29
+
- Add the plugin docs in `apps/docs/src/content/docs/docs/plugins/<docs-slug>/index.mdx` and `apps/docs/src/content/docs/docs/plugins/<docs-slug>/getting-started.mdx`.
30
+
- Add the English tutorial in `apps/web/src/content/plugins-tutorials/en/<tutorial-slug>.md`.
31
+
- The tutorial slug must match the GitHub URL slug used by `item.href` on the plugin entry because `/plugins/[slug]` resolves from that repo slug. Examples:
- Register documented plugins in `apps/docs/src/config/sidebar.mjs` so they appear in the Starlight plugin sidebar.
35
+
- Register documented plugins in `apps/docs/src/config/llmsCustomSets.ts` so they appear in the docs search and LLM sets.
36
+
- Refresh metadata after adding a plugin with `bun run fetch:stars` and `bun run fetch:downloads`.
37
+
- Validate the change with `bunx prettier --write <touched-files>` and `NODE_OPTIONS=--max-old-space-size=16384 bunx astro check` in both `apps/web` and `apps/docs`, or `bun run check` from the repo root.
<p>{plugins.length} plugins currently resolve from the live Capgo registry. Dedicated docs open when available, and repository links remain visible for the rest.</p>
0 commit comments