Mosaic for Confluence

Capable recognises 15 macros from Mosaic for Confluence (Kolekti). 12 of them convert, and 3 are detected and reported without being changed.

A reported-only macro is left exactly as it is on the page. It is counted so you can see how much of it you have, and decide what to do about it, but nothing is rewritten.


#At a glance

Macro

Becomes

Support

Background

Capable Background, or a native Confluence panel

Converted

Cards

Capable Cards

Converted

Interactive Banner

Capable Banner

Converted

Button and Button Group

Capable Buttons

Converted

LaTeX

Capable LaTeX

Converted

Tooltip

Capable Tooltip

Converted

Progress Tracker

Capable Progress Tracker

Converted

Footnote

Capable Footnote

Converted

Footnotes Summary

Capable Footnotes Display

Converted

Alerts

Native Confluence panels

Converted

Expand

Native Confluence expand

Converted

Tabs

Native Confluence expands

Converted

Smart Page Editor

Not converted, reported only

Reported only

BibTeX Reference

Not converted, reported only

Reported only

BibTeX Display

Not converted, reported only

Reported only


#What each one does

#Background

Migrates to

Capable Background, or a native Confluence panel

Support

Converted

A background with an image becomes a Capable Background macro. A background with no image becomes a plain native Confluence panel coloured to match, not a Capable macro at all.

What survives the move

  • Image, background colour, text colour, opacity, image position, side spacing, text alignment, height setting and corner radius

  • Stock library images are rewritten to keep loading from the vendor's own servers, so migrated pages still depend on the vendor's image hosting for those.

  • The on-screen note claims corner radius and minimum height are not migrated. They are. The note understates what carries across.

#Cards

Migrates to

Capable Cards

Support

Converted

What survives the move

  • Per card: title, body, image, background colour, text colour and destination link (resolved to a Confluence page where possible)

  • Column count (limited to 1–6, default 3), text alignment as card alignment

What does not come across

  • Colour palettes

  • Migrated cards are pinned to a fixed column count rather than Capable's responsive mode, deliberately matching how the original rendered.

  • The on-screen note says alignment is not migrated. It is.

#Interactive Banner

Migrates to

Capable Banner

Support

Converted

What survives the move

  • Per slide: title, body, button text, image, image description and link

  • Auto-scroll on/off and its interval (limited to 2–60 seconds)

What does not come across

  • Theme and opacity options, migrated banners get a fixed look (a standard dark overlay, standard corner rounding, no shadow, no border, no accent colour)

#Button and Button Group

Migrates to

Capable Buttons

Support

Converted

What survives the move

  • Title, link, and the button style (filled, bordered or text)

  • A group's alignment and whether it ran horizontally or vertically

What does not come across

  • Finer styling

#LaTeX

Migrates to

Capable LaTeX

Support

Converted

What survives the move

  • The formula and its block alignment

#Tooltip

Migrates to

Capable Tooltip

Support

Converted

What survives the move

  • The tooltip text

  • A tooltip with empty text is recorded as failed.

  • With "Keep source macros" on, this one migrator places the new macro before the original, where every other formatting migrator places it after.

#Progress Tracker

A horizontal three step tracker with numbered circles labelled Get Started, Create Team and Invite People, with the first step highlighted in blue.
Consecutive Mosaic step macros collapse into a single tracker, keeping the labels, the links and the order.

Migrates to

Capable Progress Tracker

Support

Converted

A run of consecutive step macros is collapsed into one Capable Progress Tracker. Step titles and links carry across, and the current step is taken from whichever step was flagged as current. Older Mosaic steps store their links as a space and page title rather than a web address; Capable looks the page up and, if it cannot be found, falls back to a Confluence search link and reports that step as unsupported.

What survives the move

  • Step titles, step links and the current step

What does not come across

  • Tracker colours and styling, migrated trackers always get Capable's default palette with controls and details shown

  • A single, isolated step macro is silently skipped, because a Capable Progress Tracker needs at least two steps. It is not converted and is not reported as failed or unsupported either, so the page count includes it but the run totals do not account for it.

#Footnote

Migrates to

Capable Footnote

Support

Converted

What survives the move

  • Footnote text and its identifier

  • Covers both the current footnote macro and the older bodied version.

#Footnotes Summary

Migrates to

Capable Footnotes Display

Support

Converted

  • Carries no settings across, the new macro is created with default configuration. Covers both the current and legacy macro keys.

#Alerts

Migrates to

Native Confluence panels

Support

Converted

Alert macros become native Confluence panels rather than Capable macros, so the pages keep working after the vendor app is uninstalled.

#Expand

Migrates to

Native Confluence expand

Support

Converted

#Tabs

Migrates to

Native Confluence expands

Support

Converted

  • Tabbed content becomes a stack of expandable sections, not tabs.


#Detected but not converted

These are found and counted so the report is honest about what is on your pages. They stay exactly as they are.

#Smart Page Editor

Migrates to

Not converted, reported only

Support

Reported only

  • Counted so you can see how many pages use it. Cannot be selected.

#BibTeX Reference

Migrates to

Not converted, reported only

Support

Reported only

#BibTeX Display

Migrates to

Not converted, reported only

Support

Reported only



Native beats a macro, where native will do.