Smaller pieces are easier to maintain. Independent components with clear focus are useful even outside of media. Components can be shared among many media solutions which simplifies development and maintenance. Media can re-use components that might already exist in the community.
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.
because of moments like that. It doesn't happen every session, but often enough we can reach out to someone new and give them the inspiration, confidence, insight, or simple kick-in-the-pants they need to take the next leap in their career, their learning, and in helping those around them grow, too. Most people we reach likely don't respond so explicitly, but speakers know they're out there. Different topics or styles will resonate for different people, but they will pick up on it.
because of moments like that. It doesn't happen every session, but often enough we can reach out to someone new and give them the inspiration, confidence, insight, or simple kick-in-the-pants they need to take the next leap in their career, their learning, and in helping those around them grow, too. Most people we reach likely don't respond so explicitly, but speakers know they're out there. Different topics or styles will resonate for different people, but they will pick up on it.
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.
When specifying dependencies in your module's .info file, you now can (and are encouraged to) specify the project that your module depends on also (since Drupal 7.40) - for example, dependencies[] = views:views_ui to declare a dependency on the Views UI module within the Views project, rather than just dependencies[] = views_ui. This extra information will help resolve ambiguities and can potentially be used by other tools in the future, for example by the drupal.org testbot or Drush to be able to automatically download dependencies that currently can't be downloaded automatically.