Skip to main content
Emil
Contributor ⭐️⭐️⭐️
December 23, 2020
Open

Syncing your published Community platform to your staging environment

Related products:CC Development Experience
  • December 23, 2020
  • 5 replies
  • 56 views

We are recently making big changes to our platform and the way it looks as we are starting to utilise the skills of other teams within the business such as our UX and UI teams to help with the experience community members receive. 

As part of this myself and our other team have been using the staging environment to trial new things. however, it’s almost impossible to imagine what these changes would look like/how they would work together as the staging environment doesnt look anything like our current platform due to in not being updated the same time the live site was. 

My idea:

My idea is for you guys to build the functionality so you can automatically sync your staging agrea to mimic/copy all of the settings/look and feel of your live site. or to have the ability to select certain settings, content or banners to be copied over to the staging area. I believe this would make it much easier for people who are utilising the staging area 

    5 replies

    Marion Frecaut
    Helper ⭐️⭐️⭐️
    December 30, 2020

    Hi @Emil, thank you for your idea. This is a very relevant idea indeed and I totally understand your use case. I'll leave this idea open to gather some votes so we get a better idea of priority :)

    Marion Frecaut
    Helper ⭐️⭐️⭐️
    December 30, 2020
    Updated idea status New → Open
    Alo
    Contributor ⭐️⭐️
    January 28, 2021

    I fully support with this idea - thought would need to be given around obfuscating users email and/or email settings so no-one receives any notifications from the staging site.

    I think for customers who haven’t adapted the look/feel of the site template, then they wouldn’t feel this feature would be necessary - but for those that have, then it feels like a necessity. I am hesitant about making a major change to the site css as I need to do it straight on the live version. The workaround is to adjust the styling in the browser code inspector but this is prone to error and very time-consuming.

    abaker
    abaker
    Contributor ⭐️⭐️
    February 6, 2021

    should we be making all of our config like groups and such on production then instead of staging?

    Amanda
    Onomatopoeia
    Onomatopoeia
    Helper ⭐️⭐️
    August 27, 2021

    Back this idea fully. Ideally, we wouldn’t be making any change to our production environment without trialling it on staging first but, as mentioned above, it’s not possible to understand how a change will truly impact prod without sufficient data on staging. 

    Being able to clone production to staging would be a huge benefit to understanding the impact of the changes we’re looking to make.

      Terms & ConditionsAccessibility statement