---
title: "Drupal config vs Site Studio packages"
date: "2022-04-05T14:45:25+00:00"
summary: "Discover why Site Studio packages are essential for managing Drupal configuration. Learn the key differences and benefits over core config management for seamless template and component handling."
image:
type: "page"
url: "/drupal-starter-kits/add-ons/site-studio/drupal-config-vs-site-studio-packages"
id: "31ced878-deae-42aa-a085-6fab84eaab69"
---

Important

You must use the Site Studio packages to manage your Site Studio configuration instead of the Drupal core configuration management system.

Site Studio leverages Drupal configuration entities for all templates, components and styles that are created using the low-code interface. As such the package export and import process utilises the Drupal core configuration management workflow at it's core, however, it is important to note that the two are not interchangeable and Site Studio's packaging system should be used due to the additional functionality it provides as highlighted below.

When using Site Studio package management alongside Drupal core configuration management the [Config Ignore and Config Split](/drupal-starter-kits/add-ons/site-studio/setup-config-ignore-and-config-split "Setup Config Ignore and Config Split") modules should also be configured.

**Import and export feature comparison:**

Drupal config

Site Studio packages

Exports configuration entities

Exports configuration entities

Imports configuration entities

Export file entity dependencies and metadata

Ignores missing file entity dependencies

Imports configuration entities

Performs Drupal validation

Imports file entity dependencies

 

Performs Drupal validation

 

Performs Site Studio validation

 

Performs Site Studio data integrity checks (optional in v6.8+)

 

Handles Site Studio entity rebuilds

Site Studio Configuration Management module
-------------------------------------------

Acquia recommends that you install the [Site Studio Configuration Management](https://drupal.org/project/sitestudio_config_management) module after you use Site Studio with the Drupal configuration management system. This module provides best-practice settings for `config_ignore` and `config_split` modules to ensure that Site Studio configuration is handled correctly during deployment synchronizations.

### Importance

Without proper configuration management rules, deployment configuration synchronizations delete critical Site Studio settings from the database, such as API keys, Agency keys, and API server URLs. This issue causes Site Studio rebuilds to fail, triggers resource exhaustion loops, and results in complete site downtime.

### Required modules

*   [****Config Ignore****](https://www.drupal.org/project/config_ignore)  
    Prevents the system from overwriting specified configuration items during import.
    
*   [****Config Split****](https://www.drupal.org/project/config_split)  
    Enables environment-specific configuration. For example, this module manages different settings for development, staging, and production environments.
    
*   [****Site Studio Configuration Management****](https://drupal.org/project/sitestudio_config_management)  
    Provides recommended `config_ignore` and `config_split` settings specifically for Site Studio.
    

### Config Ignore rules

Add the following to your `config_ignore` settings at a minimum to protect Site Studio configuration during deployments:

    cohesion.settings

Refer to the settings that [Site Studio Configuration Management](https://drupal.org/project/sitestudio_config_management) module provides for a complete list of recommended ignore rules.

Important

If Site Studio packages are not used for managing Site Studio configuration, alternative means of synchronising file entities and triggering rebuilds will need to be implemented in order for your Templates, Layouts and Styles to work as expected. Such alternative solutions may result in poor performance and unexpected behaviour.