Gatsby: What's the state of gatsby-mdx?

Created on 12 Oct 2018 · 4Comments · Source: gatsbyjs/gatsby

I would really like to start using gatsby-mdx as it clearly has immense potential!

However, I feel like the documentation doesn't (yet) do a good job of telling you how to get started. That in turn makes me wonder how mature the project itself is and how likely it is that it will continue well into the future. And even if that's a given, over what timeframe can we expect the docs to be completed?

I've seen several sites use gatsby-mdx in production so clearly that's possible. But then I don't know how many issues I would encounter attempting the same. Can someone who has walked this path perhaps chime in and report his experience?

question or discussion

Source

janosh

All 4 comments

I've used it quite a lot and it's stable enough to use. MDX itself has certain limitations, like not supporting inline JSX, but otherwise it's really good. Here are three ordered entry points to get you started with gatsby-mdx:

After reading these, assuming you're already familiar with Gatsby, I suggest diving into the kitchen sink example and looking around, changing stuff until you get a good feel on how things work. That's the best way to learn.

gatsby-mdx is an independent plugin, it's not a part of this repo, so you should direct your questions to that repo instead.

silvenon on 13 Oct 2018

👍1

@silvenon Thanks for the reply!

gatsby-mdx is an independent plugin, it's not a part of this repo, so you should direct your questions to that repo instead.

That reminds me I also wanted to ask is there a timeframe for gatsby-mdx to become an official plugin?

janosh on 14 Oct 2018

That's also a question for gatsby-mdx maintainers. Personally, I don't think it will happen because gatsby-mdx has quite a lot of things going on under the hood in comparison to most official plugins.

silvenon on 14 Oct 2018

As mentioned - gatsby-mdx is not maintained here (right now). Please ask your questions in gatsby-mdx repo.

The "official plugin" is wrong way of looking at things IMO - just because it's not in this repo doesn't mean anything. It's just maintained in other place. We really encourage people to make and maintain plugins outside of this repo. That's why we include all gatsby plugins in our plugin library and not only ones that are maintained here.