<-/.<.>/.||./.Trellis Docs

Roadmap

Last updated: 03/04/2026Edit this page

This page tracks planned features and migration tools. It reflects current intent, not commitments — priorities can shift based on user feedback.

Migration tools

Trellis already includes a Docusaurus migration script that automates content, sidebar, and frontmatter conversion. The following migration paths are planned.

Confluence

Many engineering and DevOps teams maintain large documentation sets in Confluence and find it limiting for technical docs: no version control, no PR-based review workflow, no integration with release pipelines, and content that drifts because there's no ownership or freshness signal.

The planned Confluence migration path will work from a Markdown export (via a third-party export tool) and handle:

  • Cleaning up Confluence-generated Markdown artifacts
  • Reconstructing page hierarchy into config/sidebar.ts
  • Mapping Confluence metadata to Trellis frontmatter
  • Flagging macros and embedded content that require manual attention

Notion

Notion's built-in Markdown export produces reasonably clean output. The planned Notion migration guide will cover what the export includes, what gets dropped (unsupported block types), and how to organize exported content into the Trellis content/docs/ structure.

MkDocs

A MkDocs migration script is under consideration. MkDocs projects use plain Markdown with a mkdocs.yml nav configuration, making the content straightforward to port. The main transforms needed are admonition syntax (!!! note) and tab syntax (=== "Tab"), both of which differ from Trellis conventions.

Have a request?

If there's a migration path or feature that would unblock your team, start a discussion on GitHub.

Was this page helpful?