In action on this page
TLO Calendar
get/everything/thorped/tlo-cal?o=demo
TLO Document
get/everything/posted/tlo-doc?s=https://nimdaghlian.github.io/devdemo/tlo-publishers&match=exact
This returns a TLO document generated from this page’s marked-up explanation above.
Raw HTML
<h3 id="tlo-calendar">TLO Calendar</h3>
<a href="https://next.octothorp.es/get/everything/thorped/tlo-cal?o=demo"><code class="language-plaintext highlighter-rouge">get/everything/thorped/tlo-cal?o=demo</code></a>
<h3 id="tlo-document">TLO Document</h3>
<a href="https://next.octothorp.es/get/everything/posted/tlo-doc?s=https://nimdaghlian.github.io/devdemo/tlo-publishers&match=exact"><code class="language-plaintext highlighter-rouge">get/everything/posted/tlo-doc?s=https://nimdaghlian.github.io/devdemo/tlo-publishers&match=exact</code></a>
This returns a TLO document generated from this page’s marked-up explanation above.
Tiny Little Office (TLO) stores a whole document in the URL fragment. Nothing is uploaded and there is no server copy: the link is the document. An OP publisher can build that document from query results and return the link.
What is happening?
Anything an OP relay knows about can be output in a new format using a publisher. This page demos the publishers we whipped up for Tiny Little Office since we've always wanted a document-as-api-endpoint.
tlo-cal
tlo-cal returns one calendar link for the whole result set. Each page becomes an event dated by its
postDate, and the link opens in TLO'scalapp.tlo-doc
tlo-doc returns one document link per page. The document is built from the page title and its
documentRecord.richContent, and opens in TLO'swriteapp. Each link has a 2,000-character budget; content over the budget is truncated block by block.This explanation is marked as rich content, so the tlo-doc demo below turns this page into a TLO document.
Both publishers run on next.octothorp.es until v0.7 ships.