Released 0.7.2 with support for local_icons plus color_mode & icon related bugfixes
icons.md guide for details)icons.md guide)
Rendering the source code for a full component module could be too lengthy and slow (think core_components.ex with a lot of function components in a single module)
You can now decide, per story, to render only your function’s source code.
Shipped, but not released yet.
Released 0.8.0 with a lot of stuff regarding components, attributes, and slots documentation 
Function documentation is properly rendering markdown:
Attribute and slots documentation is rendering markdown and can be expanded when written on multiple lines.
It also features a new HTML preview tab for function components
it now requires phoenix_live_view 1.0.0
phoenix_live_view ~> 1.0.x
0.8.1 is out, this is the first release ever for which I didn’t produce a single line of code.
Thank you @xxdavid @cschmatzler @sodapopcan for your contributions! 
Changelog:
@xxdavid @xxdavid @cschmatzler @sodapopcan
It’s been a few months!
Version 0.9.0 (and 0.9.1) have just been released. Most of the work focused on migrating to Tailwind 4.x, which turned out to be quite a daunting task! 
Here the changelog:
phoenix_storybook has been considerably refactored to use the latest Tailwind 4.x.phoenix & phoenix_live_view are no longer bundled in the storybook JS file
I am working on a component that optionally has a row_click attribute.
How can I pass the value of the row_click attribute (which is JS event) in my functional component for my story to be shown?
I got it working now,
attributes: %{
...
row_click:
{:eval,
~S"""
fn id ->
%JS{}
|> JS.toggle_class( "rotate-180", to: "#icon-user-with-accordion-#{id}")
|> JS.toggle_class("hidden", to: "#content-user-with-accordion-#{id}")
end
"""}
},
0.9.2 has been released!
Index module doc for details)And a big question: when is it a good time to release a 1.0.0? 
Why a 1.0.0 now?
… because why not?
We’ve been using it in production for years, so it feels stable enough!
The changelog:
handle_info/2 for parent message handling (e.g. send_update/2)
I just shipped support for permalinks to a component’s source on GitHub and GitLab.
The link includes precise highlighting of the component’s function. 
Bonus: dedicated icons for GitHub and GitLab.
Now on main, soon in 1.1.0