Remove platform-docs Docusaurus site

[manzoorwanijk]

What?

Removes the platform-docs/ Docusaurus site from the repository.

Why?

platform-docs/ is the source of the Gutenberg Framework site, a documentation site aimed at developers using Gutenberg outside WordPress. As discussed in the Core editor Slack thread, that site is no longer actively maintained, is noindex'd, and is manually synced to wordpress.org via an external script — the original goal of a dedicated site for non-WP developers never fully materialized.

Within the monorepo it has been an isolated island: a standalone package with its own package-lock.json, deliberately excluded from the root workspaces array, and with no build or deploy workflow in .github/. Removing it drops unmaintained code and a handful of stray cross-references. It can be recovered from git history if the effort is ever revived with a real commitment.

How?

• Deletes the entire platform-docs/ directory.
• Removes the now-dead references to it:
  • .npmpackagejsonlintrc.json — the ./platform-docs/package.json override block.
  • react-scanner.config.js — the platform-docs entry in the exclude list.
  • tools/eslint/config.mjs — the platformDocsConfig import and its spread (the override only targeted platform-docs/**).
  • docs/contributors/folder-structure.md — the platform-docs entry.

Historical references in changelog.txt and a release-tools test fixture are intentionally left untouched.

Retiring the live wordpress.org/gutenberg-framework/ path and its w.org sync script is handled separately, outside this repository.

Testing Instructions

1. Confirm platform-docs/ no longer exists.
2. Run npm run lint:js and confirm the ESLint flat config loads with no missing-module error for the removed override.
3. Confirm react-scanner.config.js and .npmpackagejsonlintrc.json still parse (e.g. node -e "require('./react-scanner.config.js')").
4. grep -rn "platform-docs" --exclude-dir=node_modules . returns only the intentionally-retained historical entries (changelog.txt, the release-tools test fixture).

Testing Instructions for Keyboard

N/A — no user-facing UI changes.

Use of AI Tools

This PR was authored with the assistance of Claude Code (Claude Opus). The author reviewed all changes.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: aduth <aduth@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Size Change: +1.15 kB (+0.01%)

Total Size: 8.44 MB

📦 View Changed

Filename	Size	Change
build/scripts/block-editor/index.min.js	380 kB	+279 B (+0.07%)
build/scripts/block-library/index.min.js	324 kB	+452 B (+0.14%)
build/scripts/blocks/index.min.js	57.1 kB	+52 B (+0.09%)
build/scripts/components/index.min.js	263 kB	+265 B (+0.1%)
build/scripts/edit-site/index.min.js	296 kB	+19 B (+0.01%)
build/scripts/edit-widgets/index.min.js	22.2 kB	+26 B (+0.12%)
build/scripts/editor/index.min.js	466 kB	+56 B (+0.01%)

_{compressed-size-action}

[github-actions]

Flaky tests detected in dd2bcda.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/27194643722
📝 Reported issues:

• [Flaky Test] shows post-locked modal when document size limit is exceeded #78753 in /test/e2e/specs/editor/collaboration/http-only/collaboration-document-size-lock.spec.ts

[aduth]

LGTM 👍 Thanks for pushing for this cleanup. The upside of it being an "isolated island" is it's a pretty clean and easy removal 🙂

For review, I manually inspected files changed, searched lingering references in the code, verified passing lint and build.

[ajitbohra]

Regarding the live https://wordpress.org/gutenberg-framework/ site, what is the plan for its content? Has it been migrated to a standalone repository, or is it being retired completely? I am curious if there are plans to move the documentation into the existing Handbook instead. we already have a platform section (e.g., https://developer.wordpress.org/block-editor/how-to-guides/platform/custom-block-editor/) but this target toward Custom Editor within WordPress

Gutenberg Platform is quite useful but seems to have gone stale and remains undiscovered by many.

[manzoorwanijk]

#79063 tracks its future.