Don't want Include excerpt macro to inherit restrictions

Question

Hi everyone,

we have the following use case:

content is curated and updated in a space with restrictions and parts of that content is built in the excerpt macro and should be made available in another not-restricted space.

The idea behind this is that all work on the content is done in the restricted space (for valid reasons) and parts of that content should also be made available in a non-restricted space in our site.

Unfortunately the include excerpt macro seems to inherit the restrictions from the page the referenced excerpt originally lives.

I'd be grateful for tipps for workarounds or if someone could point to a macro that is suitable for that use case. I haven't been able to find one.

Thank you!

Ruth

Kristian Klima_gtcuat · Accepted Answer

Hi @Ruth Piejko and welcome.

You ran into a very common problem with a single source authoring content that serves two purposes and must be distribute across two or more channels.

In other words, conditional content.

There is a solution but it involves 2.5 apps from the marketplace.

As far as I know, there's just one app on the marketplace that allows you to use 'conditional' content - Scroll Documents expanded by Variants for Scroll Documents by K15t. And then there's Scroll Viewport.

Essentially, Scroll Docs with Variants allow you to designate which content is public or private via a macro and Confluence labels.

You set up conditions for your variants. In our case at Emplifi, it's all content is PUBLIC except if labelled with a designated internal label (pages or variants macro).

Then we build a public site with the Viewport app that has only the PUBLIC labelled  content.

The magic of Viewport is that it builds a site independently of Confluence permissions so if your page is labelled PUBLIC, it will be in Viewport even if your space is restricted - in other words, your excerpt would appear on the site.

It sounds complex but it really takes about 30 minutes to set up :)  I'm happy to chat more if the solutions sounds intriguing but I'm sure the good folks at K15t would help too.

Anyway, in your case, you'd have to adjust your workflow a bit but the result would be an extremely flexible and pliable environment as you'd be able to use conditional content for all sorts of purposes.

Disclaimer: I don't work for K15t, we're using their apps extensively at Emplifi.