Bring back a dedicated site for "Gutenberg as a framework"

[juanmaguitar]

Bring back a dedicated site for Gutenberg's ability to be used beyond WordPress. Following the Core editor thread that led to #79034, the platform-docs site behind wordpress.org/gutenberg-framework was removed. I understand the removal (unmaintained, noindex'd, manually synced), but I think the direction was right and worth restoring properly.

Why it matters

Surfacing Gutenberg as its own project — something you can use across different frameworks and platforms, not just WordPress — is a powerful idea with a long history in this repo (see #2780 on making Gutenberg more CMS-agnostic, and #53874 on streamlining the experience of using Gutenberg as a framework, which proposed exactly this kind of dedicated site). It deserves a dedicated site and dedicated docs. The old one had a real landing page that introduced the feature well and was a great reference for developers. Nothing else fills that gap today.

Doing it right this time

If we bring it back, let's fix what caused the removal:

• An owner (a person or team to maintain it)
• Finished content with noindex removed, so it's discoverable
• An automated build/deploy instead of a manual sync
• A clear home (monorepo with CI, or its own repo)

Longer term, I'd love to see the same dedicated-site approach for other features too — the Interactivity API would be a great candidate.

I'd be happy to be the owner or person that maintains this site/docs.

References

#53874 · #2780 · #79034 · #75041

[manzoorwanijk]

If we decide to maintain it in Gutenberg, then I would suggest adding another workspace group called apps/* and putting it in apps/platform-docs to integrate it with the monorepo, instead of keeping it isolated from the rest of the monorepo.