Skip to content
Ardo News

Ardo 6.1: room for news

Publish MDX articles with shared authors, responsive images, and full-content feeds while keeping documentation versions focused on the docs.

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.

You'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.

Posts that stay with the project

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.

A publication starts with a local source directory and an author registry:

import { defineArdoConfig } from "ardo/config"

export default defineArdoConfig({
  title: "My project",
  siteUrl: "https://example.com",
  publication: {
    from: "posts",
    authors: { team: { name: "Project team" } },
  },
})

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.

Images prepared from local originals

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.

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 picture media conditions, and srcset lets the browser select a resolution. Processing is local, using Sharp and libvips.

Documentation versions have a narrower job

A release post should keep its address when the documentation moves to the next major version. The same applies to a project's homepage.

With versioning.directories, a project can select whole documentation folders, such as guide and api-reference. 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.

The release also adds CLI update checks and optional usage reporting. Reporting requires explicit consent and is separate from checking for updates; the ardo telemetry commands let you inspect and manage it.

The publication guide 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 v6.1 release notes for the complete change list.