Docs in Confluence
When your company keeps its documentation in Confluence, the design system docs can live there too. The Library stays where people and agents edit them; Confluence gets a clean copy.
Copy one page
Every Library page with docs has Copy for Confluence in its header: each component, each token page of Foundations, Accessibility and All tokens. Choose it, open a Confluence page in edit mode and paste.
What you get:
- Headings, paragraphs and lists as Confluence text.
- Tables for props (name, type, default, required, description) and for tokens (name, value, description).
- Color tokens with their hex in light and dark, beside a swatch cell painted with the color. If your Confluence drops cell colors, the hex is still there.
- Code as code blocks. A live example becomes its code and a link, See it live in Bridge: Confluence cannot run the real component.
- Links that point back to the Library page, never relative ones.
Where rich copy is not available, the page is copied as Markdown instead: paste it in a Confluence Markdown macro.
Export every page
On the Library home, Export the docs downloads a zip with one Markdown file per page (foundations/, tokens.md, components/) and an index.md that lists them all with their Bridge address.
Import the files with Confluence's Markdown importer, or paste a file into a Markdown macro. The zip is built with the site, so it always matches the pages you see.
Bridge stays the source
Each copy ends with one line: Generated from Bridge on the day it was made. Edit it in Bridge, with the page's address. Readers in Confluence know where the docs come from and where to change them. Props and tokens come from the code, so a change made in Confluence would be lost on the next copy: edit in Bridge, then copy or export again.
Live sync (planned)
Next: publish the docs to a Confluence space on each library release, from your team's own CI, with your own Confluence credentials. Bridge never holds them. Until then, copy or export after a release.