drupal8

Drupal 8's configuration system handles configuration in a unified manner. By default, Drupal stores configuration data in the database, but it can be exported to YAML files, allowing the configuration to be managed by version control. There are cases however when configuration values need to be overridden for specific purposes. Drupal 7 had the global $conf variable that was usually populated in settings.php with conditional override values for configuration. A big drawback of that system was that the overrides crept into actual configuration.

Entity create, read, update, and delete (CRUD) operations are performed by entity storage classes; see the Entity API topic for more information. Most entities use or extend the default classes: \Drupal\Core\Entity\Sql\SqlContentEntityStorage for content entities, and \Drupal\Core\Config\Entity\ConfigEntityStorage for configuration entities. For these entities, there is a set of hooks that is invoked for each CRUD operation, which module developers can implement to affect these operations; these hooks are actually invoked from methods on \Drupal\Core\Entity\EntityStorageBase.

The YAML Form module is a form builder and submission manager for Drupal 8.

The primary use case for this module is to:

Build a new form or duplicate an existing template
Publish the form as a page, node, or block
Collect submissions
Send confirmations and notifications
Review submissions online
Download submissions as a CSV

Date Range field, Moderation States, Outside In, Place Block

uninstalling and re-enabling modules every time we have a new migration to be registered is annoying.

To solve this we're going to add some Drush commands to our custom module to do the registration without uninstalling the module.

uninstalling and re-enabling modules every time we have a new migration to be registered is annoying.

To solve this we're going to add some Drush commands to our custom module to do the registration without uninstalling the module.

The Configuration Installer is a installation profile that takes over the Drupal installer and allows sites to be created from existing configuration.

This is an installation profile and needs to be put in /profiles in order to work.

The Configuration Installer is a installation profile that takes over the Drupal installer and allows sites to be created from existing configuration.

This is an installation profile and needs to be put in /profiles in order to work.

As time goes on, I imagine more and more contrib modules will make use of Composer dependencies. As soon as your Drupal site needs just one contrib module with Composer dependencies, your entire site needs to be managed with Composer.

As time goes on, I imagine more and more contrib modules will make use of Composer dependencies. As soon as your Drupal site needs just one contrib module with Composer dependencies, your entire site needs to be managed with Composer.