This session mainly talks about how we can separate out the configuration management for Drupal core and Site studio.

Why to do this?

If Site studio configurations are managed like any other configs via drush cim/cex, it is prone to config import errors and it is observed that with initial setup and even when a new content type pushed by using incremental change, the cim used to always fail 1st time and required to be run at least 2 times to be passed.

What is the solution?

With the help of contributed module Site Studio Sync, we were able to setup a separate import/export of Site studio configuration packages using command –

drush sitestudio:package:import

drush sitestudio:package:export

Other contributed modules like Config Ignore, Config Split also plays a major role in this approach and need to be configured too for the setup which will be explained in this session.

What was the result when this approach was followed?

Error on cim do not occur anymore so cim need to run only 1 time. Also, a new command for site studio config import is added in pipeline to import site studio related configurations.

What all topics will this session cover?

1. Speaker intro.
2. Example of error coming when this approach is not being followed
3. Brief introduction to Site Studio Sync contributed module.
4. All steps explanation and execution by speaker 1 by 1 required to separate Drupal core config and Site Studio configs.
5. Output demo by showcasing error resolved after the steps followed.
6. Q&A