<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://duvlify.dev/updates.xml</id>
  <title>Duvlify documentation — recently updated</title>
  <subtitle>Duvlify is an open-source documentation framework built on Astro: write Markdown, get a static site with search, an API reference, generated share cards, and a Model Context Protocol server that lets AI agents query your docs directly.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://duvlify.dev/updates.xml" />
  <link rel="alternate" type="text/html" href="https://duvlify.dev/" />
  <updated>2026-08-10T12:21:35.000Z</updated>
  <author><name>Duvlify</name></author>
  <entry>
    <id>https://duvlify.dev/</id>
    <title>Documentation you own end to end</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/index.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Duvlify is an open-source Astro framework for documentation sites. Write Markdown, get a fast static site with search, an API reference, and an MCP server for AI agents.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/getting-started</id>
    <title>Getting started</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/getting-started" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/getting-started.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Clone Duvlify, run it locally, and understand the four things you will edit — content, navigation, identity and theme — before you deploy.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/guides/authoring</id>
    <title>Authoring pages</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/guides/authoring" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/guides/authoring.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>A file's location sets its URL. Add frontmatter, list the page in a navigation group, and use drafts and noindex to control what ships.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/guides/diagrams-and-code</id>
    <title>Code and diagrams</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/guides/diagrams-and-code" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/guides/diagrams-and-code.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Fenced code blocks get syntax highlighting, a filename header and a copy button. Mermaid fences render real diagrams that follow the reader's colour mode.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/guides/api-reference</id>
    <title>API reference pages</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/guides/api-reference" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/guides/api-reference.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Point the build at an OpenAPI document, and endpoint pages render their parameters, schemas, response tabs, and request samples from it.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/guides/deployment</id>
    <title>Deploying</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/guides/deployment" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/guides/deployment.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>The build is static output. Deploy it to Cloudflare for every feature, or to any static host, with subdomain and subpath options and their costs.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/reference/frontmatter</id>
    <title>Frontmatter</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/reference/frontmatter" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/reference/frontmatter.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Every field a page can declare, what it controls, and which fields the build requires, as defined and enforced in src/content.config.ts.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/reference/components</id>
    <title>Components</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/reference/components" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/reference/components.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>The complete component vocabulary, rendered on the page that documents it, including callouts, cards, steps, tabs, and trees.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/reference/configuration</id>
    <title>Configuration</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/reference/configuration" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/reference/configuration.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Every setting lives in src/docs.config.ts, in five exports for identity, search, theme, navigation, and agent surfaces.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/reference/theming</id>
    <title>Theming</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/reference/theming" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/reference/theming.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Accent, font, and radius are one line each in docs.config.ts, and the neutral palette derives from a single background colour.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/reference/architecture</id>
    <title>How the build works</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/reference/architecture" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/reference/architecture.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Astro with static output and no framework runtime: the join between content and config, what publication means, and every file the build emits.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/agents/overview</id>
    <title>Serving agents</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/agents/overview" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/agents/overview.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/agents/mcp</id>
    <title>The manifest, WebMCP and limits</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/agents/mcp" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/agents/mcp.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>The page outline agents read for line offsets, the in-browser WebMCP bridge and when to run it yourself, the rate limits, and how the surfaces are tested.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/agents/retrieval</id>
    <title>Retrieval</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/agents/retrieval" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/agents/retrieval.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>Two retrieval backends: a lexical index built at compile time that needs no account, and Cloudflare AI Search for hybrid semantic search when you want it.</summary>
  </entry>
  <entry>
    <id>https://duvlify.dev/agents/discovery</id>
    <title>Discoverability</title>
    <link rel="alternate" type="text/html" href="https://duvlify.dev/agents/discovery" />
    <link rel="alternate" type="text/markdown" href="https://duvlify.dev/agents/discovery.md" />
    <updated>2026-08-10T12:21:35.000Z</updated>
    <summary>How an agent finds these surfaces without being told: the API catalog, DNS-based discovery, an agent-skills index, and the places people actually look.</summary>
  </entry>
</feed>
