# The Problem
## Whose Problem
Developers and designers.
## What Problem
Need a way to both standardize code and keep track of components while maintaining consistent branding/design.
## Why it needs to be solved
As team members come in and out and projects and brands evolve, it's easy to lose track of what does and does not exist, and whether or not it meets guidelines.

# Long Term Goal
**All projects at CE will be built using components/Atomic design, and deliverables will either be or just include a "Tiny Bootstrap"**
## Fail State
Projects Glenn leads will use this or a competitor to describe and document components.

# User Journey Maps
## Developer (Current)
Receive New Project → Disect Design → Establish/Choose Framework → Custom Build Site
## Designer (Current)
Receive New Project → Design Page/Site → Get Sign Off → Send to Dev
## Developer (Target)
Receive New Project → Design Already Identifies Components → Creates / Extends Existing Framework with All Components & Brand Elements → Works With Designer / UX to Assemble Components into Page(s)
## Designer (Target)
Receive New Project → Design Predicted Components → Send Components to Dev → Work with UX to create layouts → Design Additional Components → Work With Dev to Implement Components into Page(s)

# Inspiration
* Jira
* https://standards.usa.gov/
* https://brand.ai/

---

# Eventual Updates
* ~~path override~~
* component status
* ~~arbitrary variable documentation (color palettes, sizing, etc.)~~
* ~~styleguide branding overrides~~
* arbitrary templating
  * ~~if not defined, system should guess~~
* documentation variable, meant for dev-focused information
* ~~arbitrary iframe resizing~~
* search
* ~~nesting as modifier~~
  `@modifier .emmet.style &`
* ~~arbitrary ordering of components~~