<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel>
<title>Ardo News</title><link>https://ardo-docs.dev/en/news/</link><description>Ardo News</description><language>en</language>
<atom:link href="https://ardo-docs.dev/en/news/rss.xml" rel="self" type="application/rss+xml"/>
<item><guid isPermaLink="false">urn:ardo:post:e26831f6-8a6f-45c9-9683-c51b25f88161</guid><title>Ardo 6.1: room for news</title><link>https://ardo-docs.dev/en/news/ardo-6-1/</link><pubDate>Sun, 01 Nov 2026 22:02:42 GMT</pubDate><dc:creator>Sebastian Werner</dc:creator><category>Releases</category><description>Publish MDX articles with shared authors, responsive images, and full-content feeds while keeping documentation versions focused on the docs.</description><content:encoded>&lt;p&gt;A project needs somewhere to explain what just changed. A release deserves
more context than a list of commits, and an engineering decision can be useful
well beyond its pull request. Ardo 6.1 adds a home for those stories alongside
the documentation.&lt;/p&gt;
&lt;p&gt;You&amp;#39;re reading one now. This news area uses the same publication feature
available to any Ardo project: articles authored in the repository and built
into static pages.&lt;/p&gt;
&lt;h2 id=&quot;posts-that-stay-with-the-project&quot;&gt;Posts that stay with the project&lt;/h2&gt;
&lt;p&gt;Write an article in Markdown or MDX, then give it a title, publication date,
stable ID, and author references in frontmatter. Ardo creates its page and a
chronological index. Shared author profiles keep names, portraits, and links in
one place, and an article can credit several people.&lt;/p&gt;
&lt;p&gt;A publication starts with a local source directory and an author registry:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&quot;language-ts&quot;&gt;import { defineArdoConfig } from &amp;quot;ardo/config&amp;quot;

export default defineArdoConfig({
  title: &amp;quot;My project&amp;quot;,
  siteUrl: &amp;quot;https://example.com&amp;quot;,
  publication: {
    from: &amp;quot;posts&amp;quot;,
    authors: { team: { name: &amp;quot;Project team&amp;quot; } },
  },
})
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Readers can subscribe through Atom or RSS and receive the complete portable
article. When an MDX component needs an explanation outside the website, an
explicit Markdown replacement keeps the feed useful. Drafts and future posts
stay out of the published output; scheduled posts become eligible on a build
at or after their publication date.&lt;/p&gt;
&lt;h2 id=&quot;images-prepared-from-local-originals&quot;&gt;Images prepared from local originals&lt;/h2&gt;
&lt;p&gt;Keep source images beside a post. Ardo generates responsive AVIF resolutions
and one JPEG fallback, at most 1280 pixels wide. The generated files are build
assets; the repository keeps the originals.&lt;/p&gt;
&lt;p&gt;An image retains its composition unless you supply framing information.
Optional core and preferred areas let Ardo prepare 16:10 and 4:3 crops while
preserving the subject. Presentation presets choose the crop through &lt;code&gt;picture&lt;/code&gt;
media conditions, and &lt;code&gt;srcset&lt;/code&gt; lets the browser select a resolution. Processing
is local, using Sharp and libvips.&lt;/p&gt;
&lt;h2 id=&quot;documentation-versions-have-a-narrower-job&quot;&gt;Documentation versions have a narrower job&lt;/h2&gt;
&lt;p&gt;A release post should keep its address when the documentation moves to the
next major version. The same applies to a project&amp;#39;s homepage.&lt;/p&gt;
&lt;p&gt;With &lt;code&gt;versioning.directories&lt;/code&gt;, a project can select whole documentation folders,
such as &lt;code&gt;guide&lt;/code&gt; and &lt;code&gt;api-reference&lt;/code&gt;. Their pages retain version prefixes;
everything outside stays independent of the documentation version. Existing
sites keep their previous behavior until they opt in. This site now uses that
separation for its homepage, news, guides, and API reference.&lt;/p&gt;
&lt;p&gt;The release also adds CLI update checks and optional usage reporting. Reporting
requires explicit consent and is separate from checking for updates; the
&lt;code&gt;ardo telemetry&lt;/code&gt; commands let you inspect and manage it.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://ardo-docs.dev/v6/en/guide/publications/&quot;&gt;publication guide&lt;/a&gt; covers authors, images, feeds,
localization, and setup. Metadata follows Standard.site names where applicable;
publishing to an AT Protocol account remains future work. See the
&lt;a href=&quot;https://github.com/sebastian-software/ardo/releases/tag/ardo-v6.1.0&quot;&gt;v6.1 release notes&lt;/a&gt;
for the complete change list.&lt;/p&gt;
</content:encoded></item>
<item><guid isPermaLink="false">urn:ardo:post:b84b6328-070e-46de-97d6-7edcc1000d60</guid><title>Ardo 6: React docs, served as HTML</title><link>https://ardo-docs.dev/en/news/ardo-6/</link><pubDate>Thu, 29 Oct 2026 21:10:31 GMT</pubDate><dc:creator>Sebastian Werner</dc:creator><category>Releases</category><description>A simpler static foundation, native Markdown and API tooling, and a documentation shell composed in React.</description><content:encoded>&lt;p&gt;Ardo 6 changes how a documentation site reaches its readers. Every page is built
as a complete HTML document. Guides, API reference pages, and search data are
prepared before deployment, so the result can live on a static host.&lt;/p&gt;
&lt;p&gt;For authors, the starting point stays familiar: write Markdown or MDX, bring in
React components, and keep the site beside the code it explains. The work in
this release is in making that path more direct.&lt;/p&gt;
&lt;h2 id=&quot;a-document-on-every-request&quot;&gt;A document on every request&lt;/h2&gt;
&lt;p&gt;Ardo 6 removes React Router from the site architecture. Following a page link
loads a new document. The requested content is already in its HTML, including
highlighted code and generated API descriptions. React still powers interactive
examples and site controls after hydration.&lt;/p&gt;
&lt;p&gt;That also changes the project setup. Ardo owns compatible versions of React,
React DOM, and Vite. A documentation project uses Ardo&amp;#39;s React entry points and
JSX configuration, with fewer framework dependencies to coordinate itself.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://ardo-docs.dev/assets/posts/4a68e74e8668f3c03b5f.jpg&quot; alt=&quot;An Ardo guide with its section navigation, table of contents, and highlighted configuration example.&quot;&gt;&lt;/p&gt;
&lt;h2 id=&quot;native-tools-do-the-preparation&quot;&gt;Native tools do the preparation&lt;/h2&gt;
&lt;p&gt;Ferromark compiles Markdown and MDX into React modules. Ferriki highlights code
blocks during compilation, preparing both light and dark colors. Neither job
has to wait for a reader&amp;#39;s browser.&lt;/p&gt;
&lt;p&gt;The API reference has changed too. Ardo now reads TypeScript exports through
the native TypeScript compiler and builds the reference itself, replacing the
TypeDoc integration. Components and their props belong together; signatures,
parameters, and comments become searchable pages. This release uses a pinned
TypeScript 7 nightly for that analysis.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://github.com/sebastian-software/ardo/blob/ardo-v6.0.0/docs/reports/2026-10-29-release-benchmark.md&quot;&gt;release benchmark report&lt;/a&gt;
records the measured workloads, machine, and limits behind the published timings.&lt;/p&gt;
&lt;h2 id=&quot;the-site-shell-is-react-too&quot;&gt;The site shell is React too&lt;/h2&gt;
&lt;p&gt;Headers, sidebars, and footers can be composed as children of &lt;code&gt;ArdoRoot&lt;/code&gt;. Theme,
logo, and icon are passed in JSX. This puts the site&amp;#39;s appearance and layout
where React developers already expect to work with components.&lt;/p&gt;
&lt;p&gt;There are smaller reading improvements throughout: search results include
excerpts, the narrow header gives the content more room, and the build checks
internal links and fragments in the emitted HTML. Ardo&amp;#39;s own guides are now
available in English, German, French, and Spanish, with Palamedes maintaining
translations from a shared English source.&lt;/p&gt;
&lt;h2 id=&quot;moving-an-existing-site-to-v6&quot;&gt;Moving an existing site to v6&lt;/h2&gt;
&lt;p&gt;This is a major release. Router entry files and configuration go away, native
API generation replaces TypeDoc configuration, and theme settings move to
&lt;code&gt;ArdoRoot&lt;/code&gt;. Node.js 22.22 or newer is required.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://ardo-docs.dev/v6/en/guide/releases/upgrade-to-v6/&quot;&gt;v6 upgrade guide&lt;/a&gt; walks through those
changes. For a new site, start with &lt;a href=&quot;https://ardo-docs.dev/v6/en/guide/getting-started/&quot;&gt;Getting Started&lt;/a&gt;.
The &lt;a href=&quot;https://github.com/sebastian-software/ardo/releases/tag/ardo-v6.0.0&quot;&gt;complete v6.0 release notes&lt;/a&gt;
cover the individual changes and removals.&lt;/p&gt;
</content:encoded></item>
</channel></rss>
