Variants and page titles
Hi,
we are currently evaluating the Scroll Versions Plugin. One question that arose was how it could be possible to change the page title only with the help of variants.
In case of content there is the Conditional Content macro available. This is not possible for titles though.
One solution could be to copy / duplicate the page which might have bigger implication if there is a tree of pages underneath.
The main question is how to best add a documentation that can be easily whitelabeled. The main point here is that there are a lot of small text blocks that need to be replaced depending on a variant (vendor). Maybe it's possible to have some sort of placeholders in place that get replace by the variant value. For reference see also: https://k15t.zendesk.com/hc/en-us/community/posts/360037130751-Are-there-any-recommendations-how-to-create-manage-a-documentation-with-branding
Does somebody have an idea if this is possible at all or how to work around?
-
Hi Florian. This is Roman from K15t.
Variants don't work for titles as you are already aware. I would also avoid have too many Conditional Content or Include macros on one page, especially Include ones. Yes, it's convenient that when the Variant picker is switched, some parts of the content change as well. But every new macro would increase the rendering time:
- number of Include macros = number of times to render those pages (for example, 50 Include macros would probably prevent rendering of the Confluence page. It would time out)
- Conditional Content macros work differently as they all are on the same page. The impact is light on the system.
I think the foundation of certain limitations of variants feature is based on a high expectation of its capabilities. I would suggest to look at it as a simple filtering solution. A filter would show you content or separate pages based on the selected parameter.
To summarise, it's not possible to have a dynamic page title with Variants feature. A workaround could be to create separate page trees for each customer or vendor that correspond to values in the variant picker.
Does this help?
Roman.
-
Hey Roman,
thanks for the answer. That's what I feared. So there is not really a way with Versions to build a documentation on a whitelabel bases, right?
I think the best solution then would be to render / export the whitelabel contents and make a script do the post-processing by replacing the whitelabel / vendor placeholders on the exported files.
I will think about another way to work this out. You are right that there is no use making the rendering within Confluence a lot more heavy by having a lot of macros involved.
Thanks and best,
Flo
Please sign in to leave a comment.
Comments
3 comments