Break up the component-library into smaller modules

[jaronheard]

Summary

This pull request breaks up the component-library into smaller packages, with the intention of replacing and deprecating the component library in favor of these smaller modules.

It leaves the current component-library architecture as the default for now, so all components are now duplicated across packages. The plan for moving to the new components will be detailed in an upcoming RFC.

New packages

Packages	Description	Dependencies	Dev Dependencies	Comments
ui-brand	Brand assets	ui-themes, utils	ui-docs
ui-cards	Story cards	ui-brand*, ui-core, ui-themes, utils	ui-charts	ui-brand: Logo used for loading spinner
ui-charts	Charts components	ui-brand*, ui-themes, utils		ui-brand: Logo used for loading spinner
ui-core	Common UI components	ui-themes, utils
ui-docs	Style guide and Storybook styles	ui-themes	ui-brand
ui-maps	Map components	ui-brand, ui-charts, ui-core, ui-themes, utils
ui-themes	Themes and common styles
utils	Utilities

Next steps

• [x] Ensure that the packages are broken out in a way that makes sense 
• [x] Add read-me to all packages, adjust documentation
• [x] Fix errors
• [x] Make it possible to run Storybook for component-library (yarn new-storybook)
• [x] Ensure that the correct version of Storybook is published to the web

Future work

• [x] Migration plan for component-library (https://github.com/hackoregon/civic/issues/1207)

[jaronheard]

Per discussion with @DingoEatingFuzz, making the following adjustments:

• Removing ui-labs, in favor of developing within project packages and marking components experimental
• Removing ui-platform in favor of developing within project package
• Will check to see the size of ui-cards and ui-core? Could they bundled?

[ghost]

I can't provide the caliber of technical review that @DingoEatingFuzz can, so I'll focus on participatory design aspects. These are probably the kinds of things that I'd put in an RFC about the migration process:

• Should we transition all apps using the existing component library to this modular version and completely remove the old library? It would be ideal to preempt confusion about which library to use and I could see a newer dev thinking it's maybe easier to use the all-in-one-place-but-deprecated-and-enormous library. Alternatively, if migrating all apps using the deprecated library is hard, this could probably be accomplished with good documentation, but they'll need to be migrated over eventually anyways if we want them to benefit from component library updates (and keep our brand identity synced across apps)
• I'm a bit concerned about having READMEs that just contain links to storybook because contents and instructions may be different for different versions. Also, they aren't even linked to specific storybook areas — perhaps those structures should line up? The READMEs should probably contain at least basic pertinent info and then link out to storybook with a message like "see the latest version and how to use it on storybook"

[jaronheard]

@Dianna, thanks for the review! In response to your bullets:

Should we transition all apps using the existing component library to this modular version and completely remove the old library?

See #1207 for details on your first bullet, and let me know if you have further comments after reviewing that.

I'm a bit concerned about the READMEs (sic)

Agreed, I'll flesh out the READMEs per your suggestion. I did the minimum viable READMEs as part of my first PR with the expectation that I'd fill them out a bit once we knew how everything was shaking out, so thanks for the reminder.

[jaronheard]

1. There are some duplicated files across packages. Are those intentional or by accident?

The duplicated files that you identified was accidental. I've removed the extraneous asset folder that existed in ui-charts

2. What's the deal with the .toMove files? Is that part of a multistep rollout or something?

Yep, rather than update 2018 to use the new components now, I'm going to do that in a separate PR. The components that will live within 2018 are in a temporary .toMove folder, and will live within src in the future.

The tarball size comparison[1]:

1. For some reason Bundlephobia fails on the component-library ... I was able to get a direct comparison using this tool.

[jaronheard]

Ok, I think this is ready now -- the comments have either been resolved, or incorporated into #1207.