feat: migrate plugin directory to docusaurus-plugin-showcase#51
Merged
Conversation
…wcase Replace the hand-rolled plugin directory page with the showcase plugin using the built-in pluginsPreset. Data moves from a TSX array to individual YAML files in data/plugins/ (75 entries total). - Install @homotechsual/docusaurus-plugin-showcase - Add plugin to docusaurus.config.ts with pluginsPreset at /plugindirectory - Complete the 24 missing YAML files and rename maintenanceStatus to status in the 51 existing files to match the plugin schema - Remove src/pages/plugindirectory/ and src/data/plugins.tsx - Update HomepageFeatures to remove the now-unavailable pluginCount import Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The local schema at static/schema/plugin/ used `maintenanceStatus` and allowed `compatibility`, conflicting with the showcase plugin's own schema which uses `status` and additionalProperties: false. This caused IDE false positives and three data files to fail showcase validation (rdilweb.template, milessj.typedoc-api, silva-nick.portfolio). - Remove all static/schema/plugin/ JSON files - Strip yaml-language-server schema comments from all 75 plugin files - Fix stray `- 3` lines in rdilweb.template and milessj.typedoc-api - Remove disallowed `compatibility` field from silva-nick.portfolio Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…idation - Add altor-lab.search-altor YAML (missed from PR #47 which added it to plugins.tsx on main) - Restore static/schema/plugin/ with a single 1.0.0.json that mirrors the showcase plugin's own validation schema (status not maintenanceStatus, additionalProperties: false, no compatibility field) - Re-add yaml-language-server comments to all 76 plugin files pointing at the new schema so IDE validation matches what the build actually enforces Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Keep deletion of src/data/plugins.tsx (replaced by YAML files) - Resolve add/add conflict in altor-lab.search-altor.yaml by using the new schema URL and status field (dropping maintenanceStatus/compatibility) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
⚡ Successfully deployed to Cloudflare Pages!
|
homotechsual
added a commit
that referenced
this pull request
Jun 26, 2026
feat: migrate plugin directory to docusaurus-plugin-showcase
homotechsual
added a commit
that referenced
this pull request
Jun 26, 2026
feat: migrate plugin directory to docusaurus-plugin-showcase
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@homotechsual/docusaurus-plugin-showcaseusing the built-inpluginsPresetsrc/data/plugins.tsx) to individual YAML files indata/plugins/src/pages/plugindirectory/andsrc/data/plugins.tsx@docusaurus/fasterand modernises the Docusaurus configstatic/schema/plugin/) which conflicted with the showcase plugin's own validation schemaData file cleanup
Three YAML files had migration artifacts causing showcase validation failures (items were silently skipped at build time):
rdilweb.templateandmilessj.typedoc-api— stray- 3line left afterstatus:from the oldcompatibilityfieldsilva-nick.portfolio— disallowedcompatibilityproperty (showcase plugin schema usesadditionalProperties: false)All
yaml-language-serverschema comments were also removed from the 75 plugin files as the local schema was inconsistent with what the showcase plugin validates against.Test plan
yarn buildcompletes with no showcase validation errors/plugindirectory/with all 75 plugins🤖 Generated with Claude Code