Panel with Martin Kavalar and David Vujic
summary
Discussion compares Clerk and Nextjournal integration, shows the example clerk-demo repo for reproducible notebooks, and describes Clerk features: per-form with-viewer/with-viewers overrides, per-cell hiding, and a caching layer planned for team-shared cached results. Storybook usage with storybook + shadow-cljs delivers fast component feedback and viewport testing but runs into webpack-version conflicts; deployment uses AWS Amplify for static sites and backend glue. No in-browser full code editing planned for Clerk; next steps are sharing UX and distributed caching.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:39Automated Tools or Documentation
- 9:12Can You Hide the Utility Functions in Clerk
- 9:54How Do You Approach Using Global State
- 13:13How Does Storybook Compare to Other Solutions
- 14:42Experimenting with Css Frameworks
- 22:22Challenges
