This article was originally written based on the Spark distribution. Installation profiles are like modules Installation profiles in Drupal have all the functionality of modules, including access to hooks and plugins and, critically, the ability to provide configuration for your site in the form of .yml files. Picking a machine name First, you need a machine name for your profile. This is a name consisting of lowercase letters and underscores only. From here on, all references to profilename imply the profile machine name. E.g if your profile is for Acme starter kit valid profile machine names would be acme_starter_kit acme_starter acme_starter_profile acme_kit the following would be invalid acme-starter-kit acme-kit This is because profiles are just like modules, and hence can implement hooks, - but acme-kit_form_alter would not constitute a valid PHP function name. Creating the file structure Your installation profile will reside in its own profilename directory in the /profiles directory of a Drupal 8 site.…

Problem When exporting a full export there should be an option to export all of the configuration without UUIDs, so that I can—if I want to—import my config into a site that was not cloned from the site I am exporting from, but shares the same codebase. This is already a common use case for me and will be, I think, at least as common as importing from a clone. Proposed resolution Either