Great talk! Now all of those tweets make sense! With Cory's voice, those are more welcoming. I hope he will start doing fireship style100 second video on topics along with his tweets.
What Cory shared is that if you want to document your components you commonly use a 3rd party app/project like storybook with its own build process/deploy so you have to maintain a second "product" sorta say. So he's suggesting adding the components documentation directly alongside the react code, the "fork" part is like rendering conditionally 2 separate apps given in this case an env var, so you just have to "maintain" a single codebase.
Very very good, thank you Cory
such a great talk!
AWESOME!!
Great talk! Now all of those tweets make sense! With Cory's voice, those are more welcoming. I hope he will start doing fireship style100 second video on topics along with his tweets.
Can someone explain what he mean by fork your render @24:38
What Cory shared is that if you want to document your components you commonly use a 3rd party app/project like storybook with its own build process/deploy so you have to maintain a second "product" sorta say. So he's suggesting adding the components documentation directly alongside the react code, the "fork" part is like rendering conditionally 2 separate apps given in this case an env var, so you just have to "maintain" a single codebase.
Freakin awesome.
Love/hate this talk. Cory makes great points and I agree with most of what he says. What I don't like is the utter lack of examples
That's a wonderful point. Thanks for the feedback!
💯🫡
8:35 why we need design systems day one.. not really required if your goal is project
15:07 MUI sucks