Migrate: The core API Migrate Drupal: Provides the classes needed to migrate Drupal to Drupal 8. Migrate Upgrade: Provides a simple user interface for running migrations from Drupal 6 or Drupal 7. There is ongoing work to include more of this UI in core. Migrate Plus: This is the current home for the pieces of Drupal 7's migrate functionality that didn't make it into core.
Migrate: The core API Migrate Drupal: Provides the classes needed to migrate Drupal to Drupal 8. Migrate Upgrade: Provides a simple user interface for running migrations from Drupal 6 or Drupal 7. There is ongoing work to include more of this UI in core. Migrate Plus: This is the current home for the pieces of Drupal 7's migrate functionality that didn't make it into core.
Notice that while there are lots of OOP-isms in this project, we never really had to use the new keyword. We are not in the weeds instantiating objects, just snapping together Services, Config and finishing everything off in the Drupal UI. Once you learn how to work with Services and Dependency Injection, you'll be thinking at a higher level and you can focus on one specific task. This is one of the promises of Drupal to solve 80% of the problems for you and let you focus on the 20% of your project that is unique.
Notice that while there are lots of OOP-isms in this project, we never really had to use the new keyword. We are not in the weeds instantiating objects, just snapping together Services, Config and finishing everything off in the Drupal UI. Once you learn how to work with Services and Dependency Injection, you'll be thinking at a higher level and you can focus on one specific task. This is one of the promises of Drupal to solve 80% of the problems for you and let you focus on the 20% of your project that is unique.
Commit the composer.json changes to the repo. The files downloaded by Composer do not need to be added to the repo. You’ll see a .gitignore file that keeps them out (this was added as a part of the composer packaging). Only composer.json, .gitignore, code in /web/modules/custom and the content of the /web/sites subdirectory (other than the files directory) will be stored in the git repository.
Commit the composer.json changes to the repo. The files downloaded by Composer do not need to be added to the repo. You’ll see a .gitignore file that keeps them out (this was added as a part of the composer packaging). Only composer.json, .gitignore, code in /web/modules/custom and the content of the /web/sites subdirectory (other than the files directory) will be stored in the git repository.
Release candidates also provide an opportunity to begin developing with Drupal 8, especially for: New sites. Sites that rely mainly on the expanded functionality provided by Drupal 8 core alone. Projects that will take months of development time. Sites for which Drupal 8's benefits outweigh the effort needed to port (or work around) contributed modules that do not yet have Drupal 8 versions.
Release candidates also provide an opportunity to begin developing with Drupal 8, especially for: New sites. Sites that rely mainly on the expanded functionality provided by Drupal 8 core alone. Projects that will take months of development time. Sites for which Drupal 8's benefits outweigh the effort needed to port (or work around) contributed modules that do not yet have Drupal 8 versions.