ACSF & Drupal and Your Platform

https://docs.acquia.com/site-factory/

Platform Vs Site

• All features available in the base platform will be available to all sites

• All development must consider the creation of new sites as well as updating existing sites

• Discourage the use of one-off features that will only be used on a single site

• Abstract components for reusability

Common mistakes

• No​ ​planning,​ ​or​ ​not​ ​enough​ ​planning.​

• Building a website first.

• Starting​ ​to​ ​build​ ​before​ ​gaining​ ​alignment​ ​among​ ​platform​ ​users.​

• Not​ ​following​ ​an​ ​MVP​ ​approach​ ​for​ ​the​ ​demo​ ​site.​

• Not​ ​gaining​ ​sign​ ​off​ ​on​ ​the​ ​demo​ ​site/demo​ ​profile​ ​before​ ​proceeding​ ​with​ ​site​ ​development.​

File Structure

root
  ├── blt      - Contains custom build config files for CI solutions
  ├── box      - Contains DrupalVM Configuration (optional, created by `blt vm`)
  ├── config   - Contains Drupal 8 configuration files
  ├── drush    - Contain drush configuration that is not site or environment specific
  ├── docroot  - The drupal docroot
  ├── hooks    - Contains Acquia Cloud hooks (optional, created by `blt recipes:cloud-hooks:init`)
  ├── patches  - Contains private patches to be used by composer.json
  ├── reports  - Contains output of automated tests; is .gitignored
  ├── tests    - Contains project-level test files and configuration
  ├── vendor   - Contains built composer dependencies; is .gitignored