Feature config

Use one typed config object to disable optional layout and post features without copying theme components.

Base layout

---
import { PapyrusBaseLayout } from "astro-papyrus/components";

const features = {
  header: true,
  footer: true,
  scrollHeader: true,
  search: false,
  rss: false,
  themeControls: true,
  poweredBy: true,
};
---

<PapyrusBaseLayout title="Minimal page" features={features}>
  <p>No search icon and no RSS icon on this page.</p>
</PapyrusBaseLayout>

Post layout

---
import { PapyrusPostLayout } from "astro-papyrus/components";

const features = {
  share: false,
  toc: false,
  postTags: true,
  aiMetadata: true,
  sourceActions: false,
  postStats: false,
  postSideLinks: false,
  adjacentPosts: false,
  backToTop: false,
};
---

<PapyrusPostLayout title="Minimal post" siteTitle="My site" features={features}>
  <p>Rendered without share, TOC, source actions, stats, or adjacent links.</p>
</PapyrusPostLayout>

SEO and social metadata

Papyrus layouts emit the metadata a small public site normally needs: titles, descriptions, canonical URLs, Open Graph, Twitter cards, RSS discovery, and post JSON-LD. Hidden posts stay out of public indexes. Use explicit robots frontmatter when a direct page should emit directives such as noindex, follow.

The build also generates social preview images for the homepage and every post. When a post has cover, the generated card can use that image as part of the card while still keeping the final output at the correct social-card size. Posts without a visible cover still get a generated Open Graph and X card.

papyrus.config.toml also supports generic verification meta tags, opt-in analytics, typed custom head entries, and optional security.txt output. Keep analytics disabled by default, then enable only the provider a site actually uses.

Base path deploys

Internal URLs in shared layouts and list components go through withBase() and related helpers such as stripBase(), stripLocale(), getAssetPath(), and getRelativeLocaleUrl(). This keeps navigation, post links, RSS links, favicon assets, covers, tags, collection links, adjacent posts, project cards, and 404 suggestions working when Astro is deployed under a subdirectory.

Search, tags, sitemap, and robots

Public posts can be found through Pagefind search, tag pages, and optional per-tag RSS feeds. Regenerate the sitemap during every build so new posts, tag pages, profile pages, project pages, and collection routes are included automatically. Papyrus also includes a dynamic robots.txt route that reads the site URL, keeps crawl rules near site config, and points crawlers to the sitemap index.

When [security_txt] has a contact, Papyrus publishes /.well-known/security.txt and /security.txt. Without a contact, those routes stay absent.

Plugin contract

Community plugins stay small: they declare capabilities, optional feature defaults, and site-owned integration points. They do not mutate Papyrus internals. Routes stay native Astro pages in the consuming app unless a plugin explicitly documents a route capability.