loading...

re: Introducing mdjs - interactive demos everywhere VIEW POST

FULL DISCUSSION
 

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.

 

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 πŸ€”

 

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?

markdown supported usage of HTML right from the start πŸ‘

we use details/summary a lot like this

<details>
<summary>Example config</summary>

## Details for the config
Some text

</details>

and as web components are "normal" html tags they will work just fine as well πŸ‘
e.g. you could do

<my-details>
<my-summary>Example config</my-summary>

## Details for the config
Some text

</my-details>

to bring in your design/ux/animations/...

Code of Conduct Report abuse