Hey folks,
Just wanted to drop in and chat about a little adventure we're embarking on: migrating from Confluence Data Center to Confluence Cloud. As you might guess, it's not all sunshine and rainbows—and as you should know, User Macros are waving us goodbye in the Cloud version. 🌩️
Now, we could rewrite them using Forge, but we're taking this as a sign from the tech gods to declutter some of our legacy digital workspace. So, here's the game plan: we're going to stealth-mode these macros. We don't want to just nuke 'em because that would break existing content, and we're not about that life. Existing one should continue to work until we work with content owners to move to an alternate cloud-supported solution.
Instead, we're going to ninja our way into the Custom HTML section and sprinkle some CSS magic to make these macros play hide and seek. Check this out:
<!-- Add this in the "At end of the HEAD" section -->
<style type="text/css">
li#macro-loremipsum,
li.autocomplete-macro-loremipsum,
li#macro-rss,
li.autocomplete-macro-rss {
display: none !important;
}
</style>
This little snippet is our invisibility cloak. It'll hide the macros from the MacroBrowser and the autocomplete, so our users won't be able to add more of them. Pretty neat, right?
But let's be real, we know our users are clever cookies. They might copy pages, use old templates, or dive into the source editor to bring back the forbidden macros. And hey, kudos to them for the hustle, but we're trying to keep our house in order before the big move.
So, have any of you gone through this kind of digital decluttering? How did you tackle it? Did you find a cooler trick, or maybe you just went full Marie Kondo on your macros? Would love to hear your stories or any tips you've got up your sleeve.
In the meantime, we'll be here, playing whack-a-macro until we're all settled into our new Cloud home.
Catch you in the comments, Matt
