● Obscure Netlify Subdomain
URLminder needs a public URL, which rules out anything private. The workaround is obscurity. Deploy the rendered manuscript feed to Netlify under a subdomain that's a long random string rather than a chosen name, eg. x7q2m9vb4k1p.netlify.app.
No custom domain, no link from this site, no sitemap entry. The only two places that string exists are the Beeminder goal configuration and the Netlify dashboard. The manuscript stays functionally private while still satisfying an Odometer-type goal that has to read a publicly fetchable page.
It's the same trade cool URIs warn against for anything meant to last, an unmemorable path is fragile if it ever needs to be shared on purpose. I think that's fine here, as the point is that it's never shared.
Deploys straight from the render script's output directory, same netlify deploy --prod flow as other static sites, just pointed at one .txt file instead of a build folder.
- Links to
- URLminder · rendered manuscript feed · cool URIs · render script's
- Linked from
- pico.sh · Writerdeck · Manuscript Render Script