Hi, first of all, thanks for this awesome library! It's a game changer!
I have a few issues related to components docs, so I am going to create an issue for each of them. The first thing is that component docs are completely unstyled.
For example, if I use the following docs for PhoenixStorybookDemo.Components.Button.button/1
@doc """
A simple button. When clicked, triggers a `boom` event.
This button is:
* great
* awesome
* stylish
## Example
<button label="Click me" />
"""
then it looks like this in the Storybook:
Notice that the list does not have any bullets and the heading looks just like normal text.
It is due to the Tailwind Preflight which is effective on the whole page, including the docs. I think, something like the prose class from Tailwind Typography should be used on the docs. In our company's Storybook, we are currently using this hackish workaround in our CSS:
I believe something like this (probably more elaborated, e.g., with different styles for h3 and h4) should be baked directly into Storybook, so that the docs are formatted out-of-the-box. What do you think?
Hi, first of all, thanks for this awesome library! It's a game changer!
I have a few issues related to components docs, so I am going to create an issue for each of them. The first thing is that component docs are completely unstyled.
For example, if I use the following docs for
PhoenixStorybookDemo.Components.Button.button/1
then it looks like this in the Storybook:
Notice that the list does not have any bullets and the heading looks just like normal text.
It is due to the Tailwind Preflight which is effective on the whole page, including the docs. I think, something like the
prose
class from Tailwind Typography should be used on the docs. In our company's Storybook, we are currently using this hackish workaround in our CSS:I believe something like this (probably more elaborated, e.g., with different styles for h3 and h4) should be baked directly into Storybook, so that the docs are formatted out-of-the-box. What do you think?