Change Details

####Background Can we communicate a way that teams should be able to save their configuration in a format that would be picked up later by the Community Configuration UI when Growth deploys it. This should save teams time in having to re-implement bits of what their working on to suit the community configuration UI. I know we have some way of saving the configuration object on wikis as far as I can tell, but I acknowledge that we may also approach this in a new way than what we're doing for Growth Configuration.

####Background Can we communicate a way that teams should be able to save their configuration in a format that would be picked up later by the Community Configuration UI when Growth deploys it. This should save teams time in having to re-implement bits of what their working on to suit the community configuration UI. We can considered this since teams that intend to use community configuration may finish their hypothesis work before we deploy community configuration. I know we have some way of saving the configuration object on wikis as far as I can tell, but I acknowledge that we may also approach this in a new way than what we're doing for Growth Configuration.

####Background Can we communicate a way that teams should be able to save their configuration in a format that would be picked up later by the Community Configuration UI when Growth deploys it. This should save teams time in having to re-implement bits of what their working on to suit the community configuration UI. We can considered this since teams that intend to use community configuration may finish their hypothesis work before we deploy community configuration. I know we have some way of saving the configuration object on wikis as far as I can tell, but I acknowledge that we may also approach this in a new way than what we're doing for Growth Configuration.