---
id: change.2026-10-25
title: Content exports and documentation checks
summary: Content exports and documentation checks.
type: changelog-entry
area: project
subarea: project-releases
canonical: /changelog/2026-10-25
date: 2026-10-25
releaseVersion: 0.1.0-alpha.6
---

# Content exports and documentation checks

> Documentation index: [llms.min.txt](https://www.shoalrun.com/llms.min.txt) · Document manifest: [documents.json](https://www.shoalrun.com/documents.json)

Navigation section: [Changelog](https://www.shoalrun.com/.well-known/shoalrun/navigation/changelog-tab-50f26fe22670.txt) (ID: changelog-tab). [All sections and pages](https://www.shoalrun.com/llms.min.txt)

Breadcrumbs: [Changelog](https://www.shoalrun.com/changelog.md) > Changelog > Content exports and documentation checks

**Published: 2026-10-25.**

**Version: 0.1.0-alpha.6.**

These October 25 changes group content exports in CLI `0.1.0-alpha.6` and optional documentation checks in our docs project.

## Reuse documentation inside an application

The [content export command](https://www.shoalrun.com/publish/content-export.md) builds shared pages into Markdown, static HTML fragments, assets, and a manifest. Applications can use those files in help drawers, onboarding screens, or other interfaces without loading Shoalrun in the browser.

Named export targets select a publication and eligible pages independently of the website's navigation. Facet selection is optional. Reader-specific sections remain visible with labels; tabs and walkthroughs retain every panel and step. Document links identify their destinations for application routing, with eligible website links used for pages outside the bundle.

Exports retain referenced local assets, notices, and API review requirements. A plain JavaScript help-drawer example demonstrates loading the bundle from an unrelated application route. Its `/help/` URL is an example; the configured path must match where the application serves the files.

## Check documentation with Manni

The [Manni integration](https://www.shoalrun.com/publish/manni.md) provides access to the project's installed Manni tools through a small launcher and existing Shoalrun audit hooks. Manni remains an optional project dependency; its configuration and built-in tools stay with Manni.

Our documentation project uses glossary references and structure rules for selected guides. A procedure test runs the quickstart's initialization, scaffolding, and build instructions in a disposable project, then verifies HTML, Markdown, navigation, and links. A separate accessibility check uses the built document list to inspect every published HTML page, including pages outside navigation.

A source citation connects one metadata explanation to its framework implementation and flags changes for review. This check needs a source checkout and runs separately from ordinary builds and isolated validation.

## Planned work

[Project status](https://www.shoalrun.com/status.md) also records optional vector-store connections as planned work. They are not required for content exports or the existing file-based retrieval path.