Preview and Export Multi-File GitHub Markdown as an HTML Bundle Before Confluence Publishing

1. Load a Public GitHub Repository in the Interactive Workbench

Open /app (or click the pre-configured sindresorhus/ky demo link below) to fetch up to 20 Markdown files (.md, .markdown, .mdx) from the repository root and docs/ directory. Pass 1 indexes every discovered Markdown file and heading anchor; Pass 2 compiles GitHub-Flavored Markdown tables, fenced code blocks, and relative file links into structured Confluence preview output.

Repository coordinate: sindresorhus/ky (branch: main)
Scoped discovery limit: Up to 20 Markdown files (.md, .markdown, .mdx) across root and docs/
Pass-1 index: Maps repository file paths + heading slugs to deterministic page targets

2. Export an Offline HTML Bundle via "Download HTML bundle"

In the workbench top bar, click the "Download HTML bundle" button. In public repository preview mode, the workbench builds a multi-page HTML bundle directly in your browser session and downloads a standalone .html file containing a sidebar table of contents, compiled headings, GFM tables, code blocks, and rewritten internal page anchors.

Workbench Action: Click "Download HTML bundle" in the workbench header
Downloaded File: docbrancher-bundle-<timestamp>.html
Included Sections: Navigation index + compiled HTML sections for each selected Markdown file in scope

3. Public Preview Asset Boundary vs Authorized Workspace Export

Some repository images are not included in public-preview exports. In public repository preview mode, only built-in sample workspace assets are embedded inline, so external or unbundled repository binary images are not embedded inline as data URIs during anonymous preview. Compiled headings, GFM tables, code blocks, and rewritten internal page links are fully included in the downloaded HTML bundle.

Frequently Asked Questions