Variants and page titles

Comments

3 comments

  • Avatar
    Roman Serazhiev

    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.

    0
    Comment actions Permalink
  • Avatar
    Florian Schuessel

    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

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev

    Hi Flo.

    Variants can be viewed as white label feature of Versions, but to a certain extent. It's not a full-blown functionality for implementing whitelabel / vendor placeholders in the documentation.

    If there is anything else I can help you with, please let me know.

    Roman.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk