This fixture exercises the generated-content markup that the WP Docs theme styles. It is intentionally small enough for reviewers to import or paste into a preview page without running a full corpus generation.

Inline Code And Anchors

Use inline code for identifiers such as wp_register_script_module(), package names such as @wordpress/interactivity, and command fragments such as wp option get siteurl. Headings should receive stable deep-link anchors in the rendered page.

Code Blocks

PHP examples should preserve indentation and stay readable on narrow screens.

<?php
wp_register_script_module(
    '@wp-docs/example-view',
    plugin_dir_url( __FILE__ ) . 'view.js',
    array( '@wordpress/interactivity' ),
    '1.0.0'
);

JavaScript examples should copy cleanly without including button text.

import { store } from '@wordpress/interactivity';

store( 'wp-docs/example', {
    actions: {
        toggle() {
            const context = getContext();
            context.open = ! context.open;
        },
    },
} );

JSON examples should support long keys and nested values.

{
  "handle": "@wp-docs/example-view",
  "dependencies": [ "@wordpress/interactivity" ],
  "version": "1.0.0"
}

Shell examples should keep prompts and flags aligned.

wp plugin activate wp-docs-example
wp option get siteurl --format=json

HTML and CSS examples should render as code, not markup.

<div data-wp-interactive="wp-docs/example">
    <button data-wp-on--click="actions.toggle">Toggle</button>
</div>

.wp-docs-example {
    display: grid;
    gap: 1rem;
}

API Reference Table

Callouts

Provenance

Last generated from the Script Modules pilot source map. Keep detailed run logs in WP Codebox artifacts.