adamziel / playground-docs-workflow

Experimenting with maintaining WordPress docs using WordPress Playground
https://adamziel.github.io/playground-docs-workflow/
11 stars 2 forks source link

Understanding the "kitchen sink" PHP extension #30

Closed flexseth closed 3 months ago

flexseth commented 4 months ago

Getting started with Blueprints

Blueprint sample

{
    "$schema": "https://playground.wordpress.net/blueprint-schema.json",
    "landingPage": "/wp-admin/",
    "preferredVersions": {
        "php": "8.0",
        "wp": "latest"
    },
    "phpExtensionBundles": ["kitchen-sink"],
    "steps": [
        {
            "step": "login",
            "username": "admin",
            "password": "password"
        }
    ]
}
flexseth commented 4 months ago

https://wordpress.github.io/wordpress-playground/query-api/

gd, mbstring, iconv, openssl, libxml, xml, dom, simplexml, xmlreader, xmlwriter

Package explanations

Existing packages that need docs

To document (new)

fileInfo

flexseth commented 4 months ago

@adamziel wonders if the kitchen-sink "light" option should be by default

flexseth commented 3 months ago

Kitchen sink discussion https://github.com/WordPress/wordpress-playground/pull/1191#issuecomment-2080230179

adamziel commented 3 months ago

Let’s contain the docs discussion in this issue.

Are there more utilities? In lieu of digging through the repo and trying to figure it out, figured I'd ask here :)

Just those

Also, are these good representations what the libraries do?

No, these extensions offer many features and can be used in various ways. There’s no need to explain beyond listing them and linking out to php.net. People who need those extensions already know, and there’s no need to rewrite php docs for people who don’t need those extensions yet.

Are they all PHP extensions?

Yes