Blygger Studio 0.35: reading blygs that live on WordPress
Until now, every blyg kept its files at fixed paths under its origin: items/{id}.json, feed.xml, items/index.json. A managed WordPress host cannot serve those paths without rewrite rules that shared hosting often forbids, so the largest CMS on the web could not publish a blyg.
Spec §16.6e changes that. A manifest may now say where everything lives, as URLs and templates. The first blyg to use it is Robert Peake's, published by his WordPress plugin Soapbox at robertpeake.com/blyg/: 853 posts, with every file on WordPress's REST routes.
Blygger Studio 0.35 reads it. This blyg subscribes to his, and here is a passage from one of his posts, quoted through his own templates:
Taking up the idea of protocols as engineered arguments, this talk explores the timeless algorithms that give poetry its power to evolve—from an ancient mnemonic device to a transformational way of being.
from Robert Peake ↗ · excerpt of v1
Publishing this sends his blyg a mention, and his blyg checks it against our surface, as ours checks his. When that check passes, §16.6e has been exercised end to end by two independent clients, which is the condition for it to become normative in the 0.4 spec.
Release notes: 0.35.0 and 0.35.1. If you run blygger-studio, apply migration 0025 before upgrading.