tailwind usage/distribution/flexibility

[josh-chamberlain]

Currently

As part of distributing the pdap-design-system package, we're using and compiling tailwindcss. This gives us upstream control over the components, but less downstream flexibility. To prevent people from making custom classes, we should recommend that they install tailwind on any downstream projects for which they would like to make custom classes.

It seems like we're gonna stick with this, so we should set people up for success:

• [x] document the tailwind configuration (linking to the config would be OK) so that people better know how to use it.
• [x] make sure people know to symlink (in CONTRIBUTING.md guide of this repo, maybe move it to README) so they can easily test updates to the design system locally
• [ ] make sure usage guide includes best practices for custom css, new components, and updates to the design system

[github-actions[bot]]

:tada: This issue has been resolved in version 2.1.6 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: