All shared code should have written documentation to show what it can be used for and what the idea behind it is.
Users should at least be able to ...
For further actions, you may consider blocking this person and/or reporting abuse
Interesting concept. Digging the simplicity of the execution, thoughtfulness towards backwards (and code editor) compatibility, lots of cool stuff going on.
Been working with MDX a lot myself, big fan of the syntax and how easy it makes including components (or straight up JS). The limitation I see with this method vs MDX is the inability to beat Markdown inside components. With this method, you essentially โejectโ to HTML, which can be tricky for those looking for simpler authoring experiences.
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 storywhich 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/...
Hey @ben wouldn't it be cool if dev.to ran these?
Yes it would!