| 开发者 | matthewneilcowan |
|---|---|
| 更新时间 | 2026年10月5日 21:25 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
U+XXXX), or by glyph name.clamp() between a minimum and a maximum), or fit-to-width.aria-hidden="true".glyphs-panel/assets/js/vendor/. They load only when you open the Glyphs Panel, and they run in the browser. No font data goes to a server.
/wp-content/plugins/typography-stylist, or install the plugin from the Plugins screen.For OpenType features such as stylistic sets and swashes, the font must contain them. Many professional typefaces do. Many free fonts have few features or none. Letter spacing, line height, size, and weight work with any font. If a font does not have a feature, the feature has no effect.
Yes. Some Google Fonts have OpenType features. Read the font's specimen page to see which ones.
Yes. You can add fonts in four ways:
<script> tag).'Playfair Display', serif.Yes. For each uploaded font, Adobe font, and custom font definition, you can set fallback fonts. The browser uses them if the main font does not load.
When you delete a font, you can choose a replacement font. Content that used the deleted font then shows the replacement. You can manage these replacements on the Replacement Fonts tab. Use this when you change fonts for a rebrand.
Yes. See the Accessibility section in the description for the two-copy pattern and the word-boundary notice. Settings → Typography Stylist → Accessibility has these options:
aria-label to text that you style in a heading or paragraph block.visually-hidden, sr-only, or your own class.
No. Google's spam policies name "text that's only accessible to screen readers and is intended to improve the experience for those using screen readers" as hidden text that does not break their rules. The hidden heading and the styled copy contain the same text.
A ZIP file that contains:
The upload has these protections:
.htaccess protectionThe plugin is for the WordPress block editor. It works in a page builder only if the page builder uses block editor rich text.
The front end gets CSS only, with no JavaScript. A font loads only on the pages that use it. Font file size is the main cost, as with any web font. The JavaScript loads only in the block editor.
Open the font in the Glyphs Panel. It lists the OpenType features that the font contains, and shows every glyph for each feature. You can also read the font's documentation.
Yes. When you upload a variable font, the plugin reads its axes from the font file: weight, width, slant, optical size, and any custom axis. Each axis gets a slider in both editors, and the output is standard font-variation-settings CSS. The server reads TTF and OTF files. For a kit with only WOFF2 files, click "Detect Axes from Font File" in the font's settings to read the axes in your browser, or enter the axes by hand.
On WordPress 6.5+, the plugin adds new uploaded fonts to the WordPress Font Library automatically. You can turn this off in Options. To add older fonts, use the Custom Fonts tab, one font at a time or all together. WordPress can then use them like any Library font. In WordPress 7.1, the Font Library is at Appearance → Fonts. In earlier versions, open it from the Site Editor, in Styles → Typography. The font files stay where they are, and your existing content does not change. You can remove a font from the Library again. Adobe Fonts and custom font definitions stay in the plugin, because Adobe fonts load from Adobe's servers.
Beta builds are pre-releases on the GitHub Releases page. Download the attached ZIP and install it from Plugins → Add New → Upload. Report bugs on the GitHub issue tracker or on the WordPress.org support forum.
typost_force_enqueue_paragraph_style_ids filter prints the CSS and loads the fonts of the styles you name on every page. See HOOKS.md.U+XXXX input.format('truetype-variations') hint was not recognized by the panel's file picker).typost_force_enqueue_font_ids filter — themes and extensions can force specific fonts to load on every page.http:// font file URLs are now upgraded to https:// before fetching, so fonts whose stored kit CSS contains absolute insecure URLs load correctly on HTTPS sites (cross-origin URLs are left untouched)
Older releases are documented in changelog.txt (bundled with the plugin) and on the GitHub Releases page.