← All releases

v0.16.0

featuredocs

New .claude/rules guidance so your project's AI agent knows about private (gated) collections, subdomain hubs, and that locking access (Cloudflare Access) is a separate manual step. Plus docs for setting it up.

Agent guidance for gated content

Sites now ship a .claude/rules/private-collections.md context file so the AI agent working in your project knows what's possible — and what isn't — for gated content:

  • private = true collections build their hub + pages but stay out of every discovery surface (sitemap, llms.txt, search, feeds, homepage, tags) and carry noindex, nofollow.
  • private does not lock access. It only hides content from discovery — the HTML is still publicly fetchable. seite has no Cloudflare Access integration; gating who can load the pages is a separate step you configure (Cloudflare Access / Zero Trust, HTTP auth, etc.).
  • Subdomain hubs render the collection's own index template, and the custom-domain attach on a subdomain's Pages project is a manual one-time step (seite only auto-attaches the main site's domain).

New sites get the rule from seite init; existing sites get it on seite upgrade.

Docs

  • Deployment gains "Custom domain for a subdomain" and "Gating a subdomain behind Cloudflare Access" sections.
  • Configuration already warns that private is not access control — now cross-referenced from the deploy guide.