npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

wp-interface

v1.0.0

Published

Foundational components for implementing a WordPress screen reusing UI patterns from the block editor.

Readme

wp-interface

Foundational components for implementing a WordPress screen reusing UI patterns from the block editor.

Get started with a UI like this in less than 5 minutes:

Screenshot of a custom WordPress Admin page with foundational UI resembling the block editor

Installation

npm install wp-interface

Setting Up Styles

It is crucial to include the package's CSS file for the components to render correctly.

It is recommended to copy the file to your plugin's assets location, as including the entire node_modules directory is discouraged. This can be automated as part of your build process.

wp_enqueue_style(
	'my-plugin-wp-interface',
	plugin_dir_url( __FILE__ ) . 'assets/css/wp-interface/style.css', // Adjust path as needed.
	array( 'wp-components', 'wp-editor' ),
	'1.0.0'
);

Usage

The App component is the main entry point. It handles the layout structure automatically. You can use the Header, HeaderActions, Sidebar, and Footer components to populate the respective areas.

import { App, Header, HeaderActions, PinnedSidebars, MoreMenu, Sidebar, Footer } from 'wp-interface';
import { Button } from '@wordpress/components';
import { __, _x, isRTL } from '@wordpress/i18n';
import { drawerLeft, drawerRight } from '@wordpress/icons';

function MyPluginScreen() {
	const labels = {
		/* UI labels for i18n go here. */
	};

	return (
		<App scope="my-plugin" labels={ labels }>
			<Header>
				<h1>{ __( 'My Plugin', 'my-plugin' ) }</h1>
				<HeaderActions>
					<Button variant="primary">
						{ __( 'Perform Primary Action', 'my-plugin' ) }
					</Button>
					<PinnedSidebars />
					<MoreMenu>
						{ () => (
							<>
								<MoreMenu.MenuGroup label={ _x( 'View', 'noun', 'my-plugin' ) }>
									<MoreMenu.DistractionFreePreferenceToggleMenuItem />
								</MoreMenu.MenuGroup>
								<MoreMenu.MenuGroup label={ __( 'Tools', 'my-plugin' ) }>
									<MoreMenu.KeyboardShortcutsMenuItem />
									<MoreMenu.ExternalLinkMenuItem
										href="https://my-plugin-website.com"
									>
										{ __( 'Learn more', 'my-plugin' ) }
									</MoreMenu.ExternalLinkMenuItem>
								</MoreMenu.MenuGroup>
							</>
						) }
					</MoreMenu>
				</HeaderActions>
			</Header>

			<div className="my-plugin-content">
				<p>{ __( 'Main content goes here.', 'my-plugin' ) }</p>
			</div>

			<Sidebar
				identifier="primary-sidebar"
				title={ __( 'Primary sidebar', 'my-plugin' ) }
				icon={ isRTL() ? drawerLeft : drawerRight }
				isPinnable={ true }
				isActiveByDefault
			>
				<p>{ __( 'Sidebar content goes here.', 'my-plugin' ) }</p>
			</Sidebar>

			<Footer>
				<p>{ __( 'Version 1.0', 'my-plugin' ) }</p>
			</Footer>
		</App>
	);
}

Localization

As seen above, the App component requires a labels prop to provide localized strings for the interface regions and the keyboard shortcuts modal.

Additionally, it supports a shortcutsDescriptions prop to provide localized strings for the descriptions for the default keyboard shortcuts available.

Here is a full list of the labels and keyboard shortcut descriptions supported. It is recommended you provide all of these to ensure your plugin's UI can be properly translated.

import { App } from 'wp-interface';
import { __ } from '@wordpress/i18n';

function MyPluginScreen() {
	const labels = {
		// Passed to InterfaceSkeleton (ARIA labels for regions)
		header: __( 'Header', 'my-plugin' ),
		body: __( 'Content', 'my-plugin' ),
		sidebar: __( 'Settings Sidebar', 'my-plugin' ),
		actions: __( 'Actions', 'my-plugin' ),
		footer: __( 'Footer', 'my-plugin' ),

		// Passed to App/KeyboardShortcutsHelpModal
		keyboardShortcutsModalTitle: __( 'Keyboard Shortcuts', 'my-plugin' ),
		keyboardShortcutsModalCloseButtonLabel: __( 'Close keyboard shortcuts modal', 'my-plugin' ),
		keyboardShortcutsGlobalSectionTitle: __( 'Global shortcuts', 'my-plugin' ),
	};

	const shortcutsDescriptions = {
		'keyboard-shortcuts': __(
			'Display these keyboard shortcuts.',
			'my-plugin'
		),
		'next-region': __(
			'Navigate to the next part of the screen.',
			'my-plugin'
		),
		'previous-region': __(
			'Navigate to the previous part of the screen.',
			'my-plugin'
		),
		'toggle-distraction-free': __(
			'Toggle distraction free mode.',
			'my-plugin'
		),
		'toggle-sidebar': __(
			'Show or hide the sidebar.',
			'my-plugin'
		),
	};

	return (
		<App
			scope="my-plugin"
			labels={ labels }
			shortcutsDescriptions={ shortcutsDescriptions }
		>
			{ /* Actual UI... */ }
		</App>
	);
}

Additionally, the MoreMenu, MoreMenu.DistractionFreePreferenceToggleMenuItem, and MoreMenu.KeyboardShortcutsMenuItem components also support specific props that help with localization. It is recommended you pass localized strings for the relevant props as well.

Contributing

Contributions to the wp-interface package are welcome. It is being developed in a monorepo alongside my other WordPress NPM packages. Please review the contributing guidelines to learn more about how you can contribute.