Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.yamuno.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Filename Patterns

Custom filename patterns let you define exactly how exported files are named, using tokens that are replaced with page-specific values at export time.

​
Available Tokens

TokenReplaced withExample
{title}The Confluence page title (slugified)architecture-overview
{date}The page’s last modified date (YYYY-MM-DD)2026-04-23
{id}The Confluence page ID123456789
Tokens are slugified automatically — spaces become hyphens, special characters are removed.

​
Default Pattern

By default, the exporter uses {title} as the filename pattern, producing files like: 
architecture-overview.md
api-reference.md
deployment-guide.md

​
Custom Patterns

Combine tokens and static text to build a pattern that fits your workflow:
PatternExample output
{title}architecture-overview.md
{date}-{title}2026-04-23-architecture-overview.md
{title}-{id}architecture-overview-123456789.md
{id}-{title}123456789-architecture-overview.md
Rule: The pattern must include at least {title} or {id} to guarantee unique filenames across the export.

​
When to Use Custom Patterns

{date}-{title} — Best for blogs, changelogs, or any content where chronological ordering matters. Files sort lexicographically by date. {title}-{id} — Best for large spaces where page titles might not be globally unique. The ID suffix guarantees uniqueness. {id}-{title} — Useful when importing into a system that uses Confluence page IDs as a primary key.

​
Folder Names

The filename pattern applies to individual page files. Parent page folders (in tree/space exports) always use the page title as the folder name, regardless of the filename pattern.