---
title: "Macro Names and description"
canonical: "https://support.covectors.io/space/CCAD/1405943842/Macro%20Names%20and%20description"
format: markdown
---
> ℹ️ ## Content Formatting Toolkit for Confluence - Nested macros migration and new Confluence Cloud editor
> ℹ️
> ℹ️ We have been going throw a long study to find how to make macros based on nested bodies logic in Server/DC to be available in Cloud despite Atlassian decision. (More details on Atlassian decision can be found [in this Jira Ticket](https://jira.atlassian.com/browse/CONFCLOUD-68323))
> ℹ️
> ℹ️ Unfortunately Atlassian decided that in Confluence Cloud, nested* rich body* macros are *not *supported. This decision affects strongly our core macros : SP Tabs, SP Vertical Nav, SP Horizontal Nav.
> ℹ️
> ℹ️ Since version 1.0 of our Cloud App, we decided to release a version that let our users use our macros within the new Confluence Cloud editor. We reworked the way our macros work where you can have a macro to group within its body the child macros but those child are bodiless and we use a mechanism of content parsing to display content within the related tab.
> ℹ️
> ℹ️ Still this solution blocked our customers from being able to migrate content containing our macros in there server/DC pages to Cloud.
> ℹ️
> ℹ️ To give the Apps editor the possibility to support App migration, Atlassian created a duplicate experience : Legacy content and new editor rendering.
> ℹ️
> ℹ️ In the legacy mode, Nested macros can function and display embedded content within a content legecy marco. Still that content can not be copied or reproduced in the page or other pages. It’s a strategy made by Atlassian to at least offer a “read only” like experience to the nested content.
> ℹ️
> ℹ️ 
> ℹ️
> ℹ️ To support both case: Users coming from Server/DC and our current Cloud users we proceeded as following:
> ℹ️
> ℹ️ 1. We released a cloud version that distinguish between Legacy content and new cloud editor where macros supporting nested bodies (related to content coming from Server/DC pages migration) are pointing to V1 of our API and macros NOT supporting nested bodies (related to macros used in new Confluence page Editor) are pointing to V2 of our API. **All macros to be used in new Editor include -cloud mention in their IDs. **
> ℹ️ 2. V1 macros supporting legacy content are NOT BROWSABLE and can be be inject by cloud users within their pages.
| **Macro Name DC | Display in Macro usage and macro browser** | **Macro Name CLOUD | Display in Macro usage and macro browser** | **ID** | **Feature details** |
| --- | --- | --- | --- |
| SP Horizontal Nav Group | SP Horizontal Nav Group | `horizontal-nav-group` | Organize content via tabulation in a horizontal display
Support for macros coming from DC migration
Render via Content Legacy Macro
Macro to be archived in January 2026 |
| SP Horizontal Nav Item | SP Horizontal Nav Item | `horizontal-nav-item` |
| N/A | SP Horizontal Nav Group [New Editor] [ARCHIVED] | `horizontal-nav-group-cloud` | Archived |
| SP Horizontal Nav Item [New Editor] [ARCHIVED] | `horizontal-nav-item-cloud` |
| |
| SP Vertical Nav Group | SP Vertical Nav Group | `vertical-nav-group` | Organize content via tabulation in a vertical display
Support for macros coming from DC migration
Macro to be archived in January 2026 |
| SP Vertical Nav item | SP Vertical Nav item | `vertical-nav-item` |
| N/A | SP Vertical Nav Group [New Editor] [ARCHIVED] | `vertical-nav-group-cloud` | Archived |
| SP Vertical Nav item [New Editor] [ARCHIVED] | `vertical-nav-item-cloud` |
| |
| Tabs Group | Vectors | Tabs Group | Vectors | `tabs-group` | Organize content via tabulation
Support for macros coming from DC migration
Render via Content Legacy Macro |
| Tab Pane | Vectors | Tab Pane | Vectors | `tab-pane` |
| N/A | Tabs Group | Vectors [New Editor] | `tabs-group-cloud` | Organize content via tabulation
Do not support nested content / bodied macros |
| Tab Pane | Vectors [New Editor] | `tab-pane-cloud` |
| |
| Progress Bar | Vectors | Progress Bar | Vectors | `progress-bar` | Advancement rendering macro: Percentage or Steps
Support for DC migration and new editor experience |
| |
| Progress Bar Advanced | Vectors | Progress Bar | Vectors | `progress-bar-advanced` | Support for macros coming from DC migration
Point to same configuration interface than Progress Bar |
| |
| Pourcentage Progress Bar | Vectors | Pourcentage Progress Bar | Vectors | `percentage-bar-advanced` | Support for macros coming from DC migration
Point to same configuration interface than Progress Bar Macro |
| |
| Footnote | Vectors | Footnote | Vectors | `sp-footnote` | Key words and listing as footnote in page |
| Footnote Summary | Vectors | Footnote Summary | Vectors | `foot-note-summary-box` |
| |
| Expander Container | Vectors | Expander Container | Vectors | `sp-expander-container` | Macros to organize content in clickable boxes with advanced setting
Support for macros coming from DC migration
Render via Content Legacy Macro |
| Expander Box | Vectors | Expander Box | Vectors | `sp-expander-box` |
| N/A | Expander Container | Vectors [New Editor] | `sp-expander-container-cloud` | Macros to organize content in clickable boxes with advanced setting |
| Expander Box | Vectors [New Editor] | `sp-expander-box-cloud` |
| |
| Tooltip | Vectors (Formerly: SP Infobulle) | Tooltip | Vectors | `sp-infobulle` | Macro to provide textual information on hoverd word |
| |
| Notification | Vectors | Notification | Vectors | `sp-notification` | Macro to provide notification in page based on time configuration and look and feel setting |
| |
| Panels | Vectors | Panels | Vectors | `sp-macro-panels` | Macro to provide panel display in page with look and feel configuration
Support for macros coming from DC migration
Render via Content Legacy Macro |
| N/A | Panels | Vectors [New Editor] | `sp-macro-panel-cloud` | Macro to provide panel display in page with look and feel configuration |
| |
| Button | Vectors | Button | Vectors | `sp-macro-button` | Macro to ensure clickable links with button formatting
Support for macros coming from DC migration
Render via Content Legacy Macro |
| N/A | Button | Vectors [New Editor] | `macro-button-box` | Macro to ensure clickable links with button formatting |
| | | | |
| Page Status | Vectors | Page Status | Vectors | `page-status` | Macro to set page status with look and feel configuration |