---
title: "Config workflow with sync packages"
date: "2022-04-05T14:26:05+00:00"
summary: "Streamline your Drupal development workflow with Site Studio's package management tools. Learn how to effectively export and deploy configuration using Sync, Config Ignore, and Config Split modules for seamless template and component building."
image:
type: "page"
url: "/drupal-starter-kits/add-ons/site-studio/config-workflow-sync-packages"
id: "ef45ad67-60a9-4542-a047-fa399c44131c"
---

Using Site Studio to build website templates, components and styles produces configuration entities which can be exported and imported using Site Studio's package management tools. You will need to use a combination of the Site Studio Sync sub-module and the contrib modules [_Config Ignore_](https://www.drupal.org/project/config_ignore) and [_Config Split_](https://www.drupal.org/project/config_split) to effectively export and deploy Site Studio configuration alongside Drupal configuration.

Development workflow
--------------------

The development workflow recommended when developing with Site Studio includes some important additional steps. The following section compares a standard Drupal development workflow with a development workflow that includes Site Studio.

### Standard Drupal development workflow

Standard Drupal development workflow usually consists of 4 stages:

1.  Development of a feature
2.  Exporting configuration changes relevant to the developed feature
3.  Committing exported configuration and any custom code relevant to the feature
4.  Pushing the changes to remote repository and reviewing work

![Flowchart with four steps: Build features, Export Drupal config, Commit Drupal config, Push changes to remote repository.](https://acquia.widen.net/content/d0eb1635-6a1b-4ba1-b382-348675461d61/web/66166810-Standard-Drupal-workflow.png)

### Development workflow including Site Studio

Developing with Site Studio adds two steps to the process:

1.  Development of a feature
2.  Exporting configuration changes relevant to the developed feature
3.  **Exporting Site Studio packages**
4.  Committing exported configuration and any custom code relevant to the feature
5.  **Committing exported Site Studio packages**
6.  Pushing the changes to remote repository and reviewing work

![Flowchart showing steps: Build features, Export/Commit Drupal config, Export/Commit sync packages, Push changes to remote repository.](https://acquia.widen.net/content/9971063d-e49f-4866-9bd1-658a0fcccd62/web/0bb2cc37-Workflow-with-Site-Studio.png)

The recommended approach as shown above, is to split your Site Studio sync packages from your Drupal config using **Config ignore** and **Config split** modules. For more information, see [Setup Config Ignore and Config Split](/drupal-starter-kits/add-ons/site-studio/setup-config-ignore-and-config-split "Setup Config Ignore and Config Split").