The limitation I see with this method vs MDX is the inability to beat Markdown inside components.
I can't really follow πwhat does "beat Markdown inside components" mean? care to elaborate π€
The only guess I have is that you mean it does not support jsx? if so yes that is currently true - although if needed we could introduce a jsx story which could support it π€
Hey all! π Iβm Ryo, a Sr. Design Technologist at PlayStation. I do web dev with React/TS/Node and game dev with Unity/C#/C++/OpenGL/DirectX. Feel free to ask me any questions! π€
Oops. Meant βWriteβ π phone autocorrected I guess.
For example, I do this in MDX projects all the time:
<PageLayout># Markdown being parsed inside JSX
Letβs me use components inline, as well as containers for content, while retaining the MD syntax for simpler authoring without writing excessive `<p>` tags π
</PageLayout>
Should work the same with Web Components if they have slots?
I can't really follow πwhat does "beat Markdown inside components" mean? care to elaborate π€
The only guess I have is that you mean it does not support jsx? if so yes that is currently true - although if needed we could introduce a
jsx story
which could support it π€Oops. Meant βWriteβ π phone autocorrected I guess.
For example, I do this in MDX projects all the time:
Should work the same with Web Components if they have slots?
markdown supported usage of HTML right from the start π
we use details/summary a lot like this
and as web components are "normal" html tags they will work just fine as well π
e.g. you could do
to bring in your design/ux/animations/...