Satori-style rendering

Nextra’s Advanced folder includes a Satori page about OG image generation. On a pure-static Taubyte website you typically cannot run a Node OG server at request time.

What you can do instead

1. Pre-render cards at build time (scripts that emit PNGs into docs/assets/images/).
2. Link out to a function that returns SVG/JSON metadata.
3. Document the pattern so product teams know where dynamic cards belong (a dedicated function + storage).

Example SVG card (inline)

<svg xmlns="http://www.w3.org/2000/svg" width="640" height="320">
  <rect width="640" height="320" fill="#0b1220"/>
  <text x="40" y="160" fill="#22d3ee" font-size="42" font-family="sans-serif">Tau Docs Kit</text>
  <text x="40" y="210" fill="#e2e8f0" font-size="22" font-family="sans-serif">Static docs · live APIs</text>
</svg>

Recommended architecture

sequenceDiagram
  participant Author
  participant MkDocs
  participant Out as /out
  participant Fn as HTTPS function
  Author->>MkDocs: markdown + assets
  MkDocs->>Out: static HTML
  Note over Fn: Optional dynamic OG later

Info

This page exists so the Advanced folder is a real multi-page section — not an empty stub.