Exporting and Importing themes is powerful

This isn't a question, more a "This is really nice" comment.

Editing custom pages (and frankly other 'themes' in verint, but in this case I'm editing a custom page) can be a time consuming process. You add widgets, such as the generic content widget, you customise blog lists, and you upload images and embed-able items.

In our case we have different environments, one we use for development, then staging and then production, and while 'out of the box' there's no push-button to migrate content from one environment to another, being able to export a theme makes life easier in this regard.

I was able to setup the custom page to look how I wanted, and then export the theme from our staging environment, load up the production environment, and import the theme.

Immaculate, everything was reproduced, re-uploaded and imported properly from the xml file, every setting, and I could even preview the changes and approve them before moving to publish them.

This functionality, I feel, is somewhat understated, and the ability for say a member in another role, such as a designer, to then stage or upload changes like this for approval by an administrator or another user, would be ideal. Having this functionality at all, is simply a time saver.

Thank you.

  • It definitely is a great feature and big time saver  

    Another great feature, which probably not many Verint Community platform users know about, is "Default group themes".

    For every “type” of page, like the group homepage, the forum thread page, blog post page, etc., you can create default themes.
    If you set that up right and configure it properly for every type of page, then for every new group you create you don’t have to drag and drop widgets on pages, change widget spacing, widget titles, imagery, page layouts, and so on.

    If at some point you want to change the design or layout of all your groups (that follow the default group theme), you can just update the default group theme and all your groups will follow the new layout/design/style.

    So that can also be a huge time saver!

  •  

    Love this callout—completely agree this functionality doesn’t always get the attention it deserves. Being able to export/import themes across environments is such a huge win, especially when you’re managing dev → staging → prod workflows. It really takes a lot of the manual rework (and risk of inconsistencies) out of the process.

    Also great point from   on Default Group Themes—that’s another one that can save a ton of time when set up thoughtfully. Between reusable themes and default configurations, you can get to a much more scalable and governed approach to managing the community experience.

    The idea of enabling more designer-focused or non-admin roles to stage and submit theme changes for approval is really interesting too. That kind of workflow would make collaboration a lot smoother and help teams move faster while still maintaining oversight.

    Appreciate you sharing this—definitely one of those features that once you start using it, you don’t want to go back Slight smile