Frontend Components Outside Main App by Adam Florczak

8
Frontend Components Outside Main App Featuring Devboard by Adam Florczak

Transcript of Frontend Components Outside Main App by Adam Florczak

Page 1: Frontend Components Outside Main App by Adam Florczak

Frontend Components Outside Main AppFeaturing Devboard

by Adam Florczak

Page 2: Frontend Components Outside Main App by Adam Florczak

Bruce Hauman defines a problem

http://bit.ly/2a8Kts3

Page 3: Frontend Components Outside Main App by Adam Florczak

App can haveone state at a time

What if we could have isolated playground

for components in multiple states?

Page 4: Frontend Components Outside Main App by Adam Florczak

devcards (ClosureStript)devboard (React)storybook (React)...

There are solutions:

Page 5: Frontend Components Outside Main App by Adam Florczak

Mobile app and web developmentfor international tech startups

What about an app in Angular 1.x...

$compile templates manually

Page 6: Frontend Components Outside Main App by Adam Florczak

How to get components back into app?

- import/require file in app with additional resolve path- or set your build system to copy required component files

Page 7: Frontend Components Outside Main App by Adam Florczak

Challenges- can be hard to integrate with complex build systems

Summary - visual overview of all states - great documentation- no code duplication - application and devboard are always in sync- no application overhaul - lighter environment, faster refresh- devboard can be helpful for designers and clients

Page 8: Frontend Components Outside Main App by Adam Florczak

Bonus

You can build devboard on pull requestallowing functionality review without checkout

and rebuilding app

storybooks.io