Often you need to create a feature with system variables to make them complete. Features itself does not provide this, but the Strongarm module does, and we'll see how to add that to the mix.

Additional resources

Features project (Drupal.org)
Introduction to Drush Series (Drupalize.Me)
https://github.com/DrupalizeMe/drupalize-lullablog (GitHub.com)

In this video we'll specifically look at using Git as a tool to aid our development process, especially when working with other people, to make sure that you don't step on each others toes and destroy work.

Additional resources

Features project (Drupal.org)
Introduction to Drush Series (Drupalize.Me)
https://github.com/DrupalizeMe/drupalize-lullablog (GitHub.com)

Features are most often used for building out actual site features. Here we look at how you can use Features to provide you with quickstart developer tools as well.

Additional resources

Features project (Drupal.org)
Introduction to Drush Series (Drupalize.Me)
https://github.com/DrupalizeMe/drupalize-lullablog (GitHub.com)

If you have more than one feature module on your site, they can sometimes step on each other and cause nasty conflicts. We'll create some conflicts and show you how this happens and how to back out of them.

Additional resources

Features project (Drupal.org)
Introduction to Drush Series (Drupalize.Me)
https://github.com/DrupalizeMe/drupalize-lullablog (GitHub.com)

When you write your own custom modules, you can make them exportable to Features as well. Here we look at how to do that with the Chaos Tools (CTools) module.

Additional resources

CTools project (Drupal.org)

Every Composer project is made up of a few standard files and directories. This tutorial provides an overview of the anatomy of a Composer project, and the essential files and directories used by Composer, including:

• What are composer.json and composer.lock files?
• What is in a composer.json file?
• What is the /vendor directory?

By the end of this tutorial you should be able to recognize the standard files and directories in a Composer project and know what they are each used for.

This tutorial demonstrates the value of using Composer. This demonstration will employ the most basic use case of using Composer to create a new, non-Drupal application that writes a message to the system log. It will encompass the fundamental concepts of Composer installation, requiring (installing) a new dependency, autoloading it, and implementing it.

In this tutorial we'll:

• Install Composer
• Use Composer to start a new project
• Use Composer to require a 3rd party dependency
• Use the required code in an example application

By the end of this tutorial you should be able to explain the value of Composer, and have Composer installed and working on your local machine.

This tutorial provides an overview of the concept of an "artifact" and provides step-by-step instructions for deploying a Composer-managed Drupal application to a hosting environment.

In this tutorial we'll:

• Define what an "artifact" is
• Look at how to use Composer and a build process to create and deploy an artifact
• Talk about the benefits of this approach

By the end of this tutorial you should have a general understanding of the steps required in order to deploy a Composer-managed project into production.

You will inevitably encounter Composer issues that require troubleshooting. This tutorial aims to provide some general troubleshooting advice for common Composer issues.

In this tutorial we'll look at:

• Common issues you'll encounter when using Composer
• Solutions to these common issues

By the end of this tutorial you should have some ideas of how to solve common issues that you might encounter when using Composer to manager your application's dependencies.

Composer packages use semantic versioning to allow you to differentiate among different releases of a project. Knowing how this works, and how to specify a version constraint when requiring a Composer package are an important part of using Composer.

In this tutorial we'll:

• Get an overview of semantic versioning
• Look at how Composer version constraints work and related best practices
• Learn how to define Composer package requirements such that you can quickly update all of your application's dependencies without breaking existing functionality

By the end of this tutorial, you should understand how semantic versioning relates to Composer, and how to specify version constraints for packages in your Composer project.

Composer is the preferred dependency management solution for PHP. List your project's dependencies in a composer.json file and, after issuing a few commands in the CLI, Composer will automatically download your project's dependencies and set up autoloading for you. Composer is analogous to NPM in the Node.js world, or Bundler in the Ruby world.

Drupal core uses Composer to manage non-Drupal dependencies like Guzzle and PHPUnit. An increasing number of contributed modules also use Composer to integrate third party PHP libraries into Drupal.

This series provides guidance for Drupal developers and site builders who would like to learn to use Composer to build and maintain a Drupal application.

It covers high-level concepts about Composer and walks you step-by-step through creating a new application, downloading PHP libraries, and implementing them using Composer!

It also covers Drupal-specific Composer configuration and provides guidance for accomplishing common Drupal tasks like updating core and installing a new module.

In this tutorial we'll:

• Familiarize ourselves with the general concepts of dependency management
• Learn about Composer and the role it plays in a PHP/Drupal project
• Learn about some advantages and disadvantages of using Composer

By the end of this tutorial you should be able to explain what Composer is, what it's used for, and make the case for using it in your own projects.