Environments/Build Process

Local Dev/Dev

• In Pantheon, we need to integrate/connect git upstream to OU Github.
• We will need the multi-dev set up with an environment for each developer and the ability to spin up new ones for specific branches of test code.
• Pantheon localdev is used for local testing environment - https://pantheon.io/docs/localdev
• Configuration Management and Config Split are the 2 most important pieces to separating config for dev/test/prod.
  • Config workflow setup in Pantheon if that is the choice - https://pantheon.io/docs/drupal-8-configuration-management
  • Devel module is needed on dev, not on test and prod. Others possible
  • Google analytics not needed on dev

Test

• Needs to be exact replica of prod. Only difference will be the current changes and testing before pushing live
• Devel and Google analytics not needed on test

Prod

• Devel not needed.
• Google analytics needed (prod only).

Migration

If Pantheon is used, there is a migration process that could help us tremendously. The instructions are here and I suggest we try this first to see how well the migration works. They can also assist in this process if we run into issues. 

https://pantheon.io/docs/migrate-manual

https://pantheon.io/docs/migrate

Another great feature of this is that we can integrate the new pantheon site into the same git repo and maintain the version/commit history. 

Content Types

Migration should take care of the content types. I suggest we review the doc and details below and possibly remove the content types BEFORE migrating. 

For list of content types to remove/keep/change, follow the content types doc - https://docs.google.com/spreadsheets/d/1-o8nu8fCs_GxAP6K9LT5u4WI_pf_heY4BKlQBgaN6NM/edit#gid=0

Short list of content types changing:

Removing completely:

• Banner Images
• Jobs
• Location Carousel
• Panel
• Picture
• Project Prospectus
• Test

Removing but keeping content:

• Policy
• Service

Rethink/restructure/replace

• Locations
• News
• Special Collections
• Units

Modules/External Libraries

If migration works well, modules will be loaded correctly. We need to evaluate the content types being removed and figure out if any of them are tied to a specific module. If that module is only present b/c of the content type, then we can remove the module.

New modules to consider adding in regards to improvements with D8:

• ckeditor
• antibot
• backup_migrate
• config_split
• conflict
• deploy
• entity_browser
• entity_embed
• externalauth
• file_browser
• media_entity
• twig_tweak
• workbench_moderation
• workspace
• phpunit - DEV/TEST ONLY

Packages/libraries

• Accessibility checker for wysiwyg/content editors
  • a11ychecker
  • balloonpanel
  • ckeditor

Look into this for pulling in external libraries

https://pantheon.io/docs/external-libraries

Views

• If the migration works out nicely, this might take care of itself. If not, we need to evaluate views and see what needs to be added, modified, removed. 

Other

• Google analytic tracking code and click events