You can extend Typography Stylist. Three modules come with it: the Glyphs Panel, Variable Fonts, and Paragraph Styles. They use the same public API that an external plugin uses. This shows that the API is sufficient.
What can an extension do?
- Add buttons to the block toolbar in both editors.
- Show its own controls in the typography panels or in the block sidebar.
- Read the current editor state: the font, weight, size, and features at the selection.
- Write properties back to the block or to the selection.
- Insert content at the cursor, with feature settings.
- Add its own tab to the settings screen.
- Filter the data that goes to the editor, and the list of available features.
- Tell the plugin which fonts or paragraph styles a page needs, with the
typost_content_font_ids,typost_force_enqueue_font_ids, andtypost_force_enqueue_paragraph_style_idsfilters.
How do the pieces fit together?
PHP hooks control what loads and what data goes to the browser. JavaScript hooks control what the editor shows and how it responds. They use window.typostHooks, a small action and filter system like the WordPress system. Custom events are the write path. An extension sends an event, and core applies the change.
This split is important. Extensions do not change block attributes directly. They describe the change that they want, and core makes it. So the plugin’s rules about selections, nesting, and accessibility still apply.
Where is the reference?
The maintainers make the detailed reference pages from the plugin’s HOOKS.md file:
- PHP Hooks: Read about the actions and filters.
- JavaScript Hooks: Read about the
typostHookssystem, the hook points, the toolbar buttons, and the editor state. - Admin Tab Extensibility: Add a tab to the settings screen.
- Extension Examples: See examples with vanilla DOM code and with React.
- Extension Plugin Template: Start a new extension from a template.
The maintainers write the REST API reference and Theme integration by hand.
Two things to know before you start
Toolbar buttons are a filter, not a container. You return a descriptor, and core shows a real ToolbarButton. If you mount your own React root in a hook container, your button is outside the toolbar’s roving tabindex. This breaks keyboard navigation for all the buttons in the toolbar.
There are two editors, and they are separate builds. The inline format is in assets/js/block-editor.js. The block is in blocks/typography-stylist/. Most hook points are in both, with typost_inline_* and typost_qft_* names. Test in both editors. Many bugs occur in only one.