To avoid development missteps and wasted effort, do not begin development on individual websites until you have defined your platform’s profile architecture as part of your Site Factory governance strategy.
When designing and implementing profiles, consider:
For instructions about enabling installation profiles on your Factory, or selecting a profile when creating a new website, see Managing installation profiles in your Factory.
When selecting a profile architecture for your platform, consider the following questions from a platform and not individual website perspective:
What global configuration is valid across websites sharing a profile?
What configurations (such as modules and permissions) must differ across environments?
What default configurations, such as theme and website name, must website builders or administrators configure?
Does your development and testing process account for creating new websites on the profile, and provide updates to existing websites created by older versions of the profile?
To work with Site Factory, an installation profile must:
Be based on Drupal core.
Include the Site Factory Connector module to provide
necessary platform management functions, such as the acsf-init
command.
Include an admin role.
For information about creating a Drupal installation profile for use with your codebase, see How to write a Drupal installation profile.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.