Kickstand | Set up deployment and npm publishing process for Kickstand

[mddilley]

A local development workflow for the Kickstand UI library has been established in https://github.com/cityofaustin/atd-data-tech/issues/3756. There are still remaining questions around when and how to publish Kickstand to the npm registry when needed. Components for this library will be identified as Moped front end development progresses and reusable components emerge.

Possibly push updates to main for testing, and then use Publish-to-npm GitHub action to create new npm versions when pushing to production

[amenity]

Discuss Moped <---> Kickstand architecture and development workflow at today's Sprint Review: Need to decide which components live in Kickstand. Once we review @lazavazav's New Project code we will discuss which components go into Kickstand.

Ultimately, Moped will be composed of Kickstand components, but it might not be efficient to put them there, first, in the interest of

• Delivering Alpha
• Making the best use of Leslie's time
• Trying out components and patterns in front of users before investing in Kickstand implementation
• Identify when a component will be useful

[amenity]

So far importing from Github branches; have a path to develop in Kickstand and see changes in another project.

[patrickm02L]

In Product Sync on 1/26/22, decided to Icebox until further notice.