v1.0.0 — Fonts that belong to your site
First stable release.
The code is byte-identical to 0.36.4. Nothing was written for the occasion — this is the build that was
installed, run across every screen and reported clean, with the version number changed to say so. The 0.x
numbering existed because only its author had ever installed it. That stopped being true, so the number stopped
claiming otherwise.
What it does
Self-hosted fonts, inside the Etch builder. Upload TTF, OTF, WOFF or WOFF2, or install from Google Fonts
without your visitors' browsers ever calling Google. The files live in wp-content/fonts on your own server
and the stylesheet is yours.
WOFF2 conversion in the browser. TTF, OTF and WOFF are compressed locally before upload — typically 40 to
65% smaller, measured at 65% on Source Code Pro — so the font is never sent anywhere but your own site. Only the
container changes: glyphs, variable axes and OpenType features are untouched.
Typography tokens. Publish a family as the site's heading or body font under the names Etch documents and
Automatic.css reads, so a framework picks it up without you writing a rule.
Per-family delivery. font-display, a fallback stack, a selector list to apply the family to, metric
overrides that hold the line height while the font loads, and preload for the cut a page renders first —
measured starting its request roughly a second before a font discovered through CSS.
Variable fonts. Axes are read from the file itself, including from a WOFF2 that has to be decompressed to
look inside. A tester for tuning an instance, and a font-variation-settings value the site actually uses.
A library that behaves like one. Enable, disable, trash and restore without losing files. A trash that is
genuinely reversible. Import and export with a real dry run that writes nothing. And if you ever remove the
plugin, the fonts and the stylesheet stay unless you ask for them to go.
Requirements
WordPress 6.0+, PHP 7.4+, and Etch. Updates ship through GitHub releases: the plugin reads a manifest and offers
the update in wp-admin like any other plugin.
Thanks
Every release from 0.20.0 onward was shaped by someone pointing at a screenshot and saying what was wrong with
it. The last four came out of exactly that, including a converter that could not load, an install that quietly
replaced font weights, and a card that was crushing its own family name.