Drupal Enablement

User Story:

As a developer, I need to understand the Drupal side of the site so that I can continue to do development on this project.

Acceptance Criteria:

Scenario 1: Nodes As an MTA site admin Given I am looking at admin/structure/types Then I can create a new content type called "drupal enablement" With a new field And an existing field

Scenario 2: Views As an MTA admin Given I am looking at admin/structure/views Then I see a new view "drupal enablement view" This view will be a listing of the content type "drupal enablement"

Scenario 3: Configuration As a developer Given I am looking at the configuration directory Then I will see the updated configuration for the following content type new fields new view

Implementation Details

() create the site locally see sync local ticket if you need more details on syncing local () create a new branch with the ticket number () create a new content type in the admin ui admin/structure/types () create a new field () add an existing field () create a view admin/structure/views () the view should be fields with the title and the fields you added to the content type () use drush to export the configuration drush cex () commit the configuration files to a pull request