[zspriggs]

The basics

• I validated my changes

The details

Resolves

Fixes #10397
Towards #7247

Proposed Changes

Adds plugins to reference docs.

Under the current setup, TypeDoc generates blockly_api.json and commits it during each release, and then the actual .md reference docs are generated based on the contents of blockly_api.json whenever docs are deployed.

This PR adds another TypeDoc run which generates a plugins_api.json during the release, and then configures Docusaurus to generate plugins docs based on plugins_api.json under their own "Plugins" folder in the reference sidebar.

Reason for Changes

Plugin APIs can/should be documented alongside our regular docs. This also serves to make the plugins more visible and searchable within our docs.

Test Coverage

Tested locally and everything works correctly

Documentation

Added info to contribute_to_docs.mdx as well as AGENTS.md and the docs README

Additional Information

There's two follow-ups associated with this PR:

• Right now, references to the core Blockly library are stated but not linked to the core API docs. Ideally we'd link back to core Blockly reference docs when applicable, but I determined that was a lot for one PR and a bit outside the scope of this issue. I've filed an issue to track this: Add links from plugins docs to core docs #10640
• The landing page for the plugins is a bare list of plugins, each with an empty description. I think it's helpful to have an overview page, so I kept it, but plugin descriptions should be added to index.ts (or index.js) for each plugin so that TypeDoc can fill in the description columns. This is a simple fix but also a lot for one PR, tracked here: Fix plugin API landing page #10641