AI and mobile readiness

Papyrus ships useful agent-readable metadata, generated indexes, and responsive UI defaults for small content sites.

AI-first primitives

• Package-level llms.txt and llms-full.txt generation for agent-readable site summaries.
• Static RSS feeds per tag.
• Static JSON indexes for posts, tags, projects, notes, and CV summary data.
• Static graph data export connecting posts, tags, projects, notes, and CV sections.
• Stable machine IDs in generated JSON indexes, graph nodes, graph edges, and search records.
• Reusable static search index for local agents.
• Per-post JSON-LD metadata for schema.org types.
• Post layout support for canonical URL, source Markdown URL, author metadata, copy Markdown, and copy citation.

Generated files include llms.txt, llms-full.txt, posts.json, tags.json, cv.json, and graph.json.

Site-specific AI extensions

• Add extra source links when a post depends on diagrams, notebooks, or external datasets.
• Add JSON-LD types for people, projects, software source code, or breadcrumbs on site-specific pages.
• Generate backlinks or related posts from Markdown links when the content model needs a knowledge graph.
• Store explicit license metadata for images, code snippets, and diagrams when licensing matters.
• Publish diagram source beside rendered SVG output for Mermaid, PlantUML, or Excalidraw workflows.

Mobile-first primitives

• Safe-area padding for phones with notches or rounded display edges.
• 44px coarse-pointer hit targets for core icon, copy, post action, tag, TOC, and back-to-top controls.
• Responsive post lists with stable cover dimensions and compact metadata.
• Collapsible table of contents and back-to-top controls designed for small screens.
• Image, SVG, and Mermaid zoom behavior that works with touch input.
• Reduced-motion handling for cursor, logo, header, dropdown, and page-transition effects.
• Profile and CV routes that share one data source across web, timeline, and print layouts.
• Static Pagefind search and generated tag pages, so mobile search does not require a server.

Mobile authoring tips

Keep post descriptions short enough to scan in list views, prefer real cover images or generated covers with stable aspect ratios, use headings in order, and preview layout-heavy changes on desktop and phone-sized screens before publishing.