Skip to content

WordPress Playground documentation #828

@adamziel

Description

@adamziel

The Ask

Let's create a comprehensive documentation for WordPress Playground. The existing one is brief and sometimes outdated. I posted a detailed outline here: WordPress/wordpress-playground#217

Where does the documentation live?

The documentation is currently published on GitHub Pages which conveniently couples it with the code – it's generated and published directly from the repository.

Technically, it lives in the gh-pages branch where it's built from:

Typedoc is great. It outputs readable pages, cross-links specific API items together, and just works. In Gutenberg we use our own tooling that does neither of these things. Here's a discussion about migrating Gutenberg docs to Typedoc.

Where should the documentation live?

I recommend a separate static site regardless of the domain (Github.io works just as well as WordPress.org).

Why?

Typedoc outputs full HTML files, which makes integration with a WordPress-based docs site inconvenient. We could use github.io just for the API reference and move the rest to WordPress.org, but then we'd lose the valuable the ability to cross-link and cross-include parts of the docs. We'd also lose the potential to use MDX.

Questions

  • Is this something we could collaborate on? Caveat: I'm on Sabbatical starting June 26th.
  • What would be the next steps here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    [Status] To doIssue marked as Tododeveloper documentation (DevHub)Improvements or additions to developer documentationneeds discussionIssue that need discussion and team's decision. Will be discussed at the meeting.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions