Mini Sites For Confluence

Mini Sites embeds a folder of HTML, CSS, JavaScript and assets live on a Confluence page. A clickable prototype, a filterable dashboard, a calculator or a small internal tool runs inline — the real thing, not a screenshot of it.

Marketplace listing: Mini Sites (Embed HTML & Prototypes) for Confluence · 35-second demo

How to use

Installation

Click Settings on your Confluence Cloud instance
Click Find new apps
Search for Mini Sites
Click Try it free to install

Publish a mini site

Edit any Confluence page and type /Mini-Site to insert the macro.
Click Upload, then Browse files…, and select the folder that directly contains your index.html.
The app validates the bundle, scans it for accidentally included credentials, and provisions it into an isolated sandbox.
Click Validate & publish, then publish the Confluence page.

Nested folders and relative paths are preserved: style.css, app.js, images/logo.png and assets/data.json all resolve exactly as they do locally.

What it is good for

Clickable prototypes — put the UI you are asking people to approve on the same page as the PRD.
Filterable dashboards — a chart plus filters over a JSON file shipped in the bundle.
Small internal tools — pricing calculators, checklist generators, troubleshooting decision trees.
Design-system demos — components rendered from the CSS the product actually ships.

Permissions and isolation

Built on Atlassian Forge: Confluence page permissions are inherited. Anyone who can view the page can use the mini site; nobody else can.
The app requests no Confluence API scopes — it does not read your page content.
Each macro instance is served from its own isolated, non-routable sandbox; there is no public URL.
Every bundle is validated and secret-scanned before it is served.

Limits

Limit	Value
Files per bundle	2,000
Maximum file size	25 MiB
Maximum bundle size	50 MiB
Required file	`index.html` at the folder root

The sandbox is static-only and has no outbound network access — external fonts, CDNs and API calls are unavailable, so bundle the assets you need. Absolute paths and ../ traversal are rejected at validation time.

Troubleshooting

Problem	Fix
`index.html` is not found	Select the folder that directly contains `index.html`, not its parent or a nested subfolder.
CSS or JavaScript does not load	Use relative paths (`style.css`, `app.js`), not absolute ones.
The upload is rejected as too large	Stay within the limits above.
The upload panel is still showing	No bundle has been published for that macro instance yet.
Viewing works but publishing is blocked	The Atlassian licence is inactive. Existing mini sites keep rendering.