Storybook monthly is where we gather to socialize, update release progress, discuss project-wide maintenance, give project updates and demos, and brainstorm about the project's future.
It's a casual public meeting, and everybody is welcome, regardless of their level of participation.
Look for a link to the zoom meeting 15 minutes before the meeting starts in the Storybook Discord's #maintenance channel. We'll share notes and screen recording afterwards.
Add to calendar 👉 2020-05-05 16:00 UTC
- Welcome
- Self-introductions
6.0 release (issue)
5 mo cycle: Apr 29 beta, Jun 1 rc, Jun 15 final
- Doc blocks
- Storybook composition
- Storybook args
- Addon essentials
- Rich props table
- Storybook for Server
- Breaking changes
- Yarn 2 support
NOTE: we are pushing the dates to make time for a first pass at overhauling the documentation. 6.0 will get a lot of attention and new users and we don't want to waste those eyeballs on outdated docs.
@yannbf @tooppaaa @gaetanmaisse @mrmckeb @ndelangen @domyen @shilman
https://us02web.zoom.us/rec/share/9OpwKJ7Oy2dIH8_11Rn2Wr5iIcf0X6a8gSEf-_tZmhwFfK6KMa4l763ONK0TlvlZ
- Markdown in repo / presentation in front-page
- storybookjs/frontpage#101
- Versioned docs
Documentation lags behind the features
- Information architecture
- Content
Multi-language? - hard to version (glamorous website had interesting versioning)
How MUI handles translations https://crowdin.com/project/material-ui-docs
Gatsby docs are basically API docs
Need to inform people that documentation is out of date
Core addons - part of the documentation experience
First attempt failed due to incompatible SB webpack magic that generates virtual modules in memory. Possible fixes:
- Write to a file system (hacky fix behind a feature flag as short-term 6.0 fix)
- Split all files into entry (as long-term 7.0 fix)
Goal to strip out most of the content from the monorepo
Standardize the way template generation is done from the CLI
- Same files / same selectors
Uniform infrastructure
- E2E testing across all the frameworks
- Fixture projects for CLI
- Framework x version x addons - parallelize it across CI
Q: How about focused tests for a specific add-on, e.g. addon-docs? A1: There’s currently e2e tests for official-storybook, can add them there? A2: Will sleep on it for a general solution