Move Existing Components Out of Emulsify Drupal

[mirzu]

┆Issue is synchronized with this Jira Story by Unito

[mirzu]

Intent

Short Term

• Move components currently shipped within Emulsify_Drupal into their own separate home. Allowing for Emulsify Drupal to be easily upgraded when we add new features.
• Make it easy for developers to include all components when started a new project
• Make it possible for developers to pull in individual components and eventually sets of components as they start working on specific parts of a project.
• provide un-opinionated, but visually appealing out of the box appearance for the base components
• The source for the higher-level components should be modular so that other teams can easily leverage this feature to create their own starting points
• Management of higher-level components should be easy to understand and require as little domain knowledge as possible. Emsulify should be easy to use regardless of what platform you are using it with and strives to add minimal complexity.
• Components should provide a starting point that facilitates additive development and avoid reductive workflows. They should provide a baseline that provides wiring to the CMS, accessibility, responsiveness out of the box while leaving styling mostly untouched.

Long Term

• Provide a system for managing higher-level components for organizations
• A cross-platform way to separate themes and branding from the component structure.
• A workflow that incorporates designer specific tooling to make Emulsify a more complete lifecycle design system tool

[amazingrando]

@amazingrando This should be considered an "epic", like in Jira.

[amazingrando]

@amazingrando Break into smaller peices.

[ModulesUnraveled]

This has already been done.

We have the Compound repo And the Emulsify CLI

Those tools together achieve the goals listed above.

There will need to be a "release" that finally removes them from Emulsify-drupal, but that will happen when we decide Compound and the CLI is our "official" workflow.