Unverified Commit 5402f099 authored by David Burrows's avatar David Burrows Committed by GitHub

Update MDX Custom Elements setup (#34175)

The current documentation for MDX Custom Element setup was not clear, ended up on https://github.com/vercel/next.js/issues/30812 before I had this configured correctly, have tried to make the config steps more explicit.




## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`
parent 2f795189
......@@ -155,7 +155,22 @@ The above generates the following `HTML`:
</ul>
```
When you want to style your own elements to give a custom feel to your website or application, you can pass in shortcodes. These are your own custom components that map to `HTML` elements. To do this you use the `MDXProvider` and pass a components object as a prop. Each object key in the components object maps to a `HTML` element name. You also need to specify `providerImportSource: "@mdx-js/react"` in `next.config.js`.
When you want to style your own elements to give a custom feel to your website or application, you can pass in shortcodes. These are your own custom components that map to `HTML` elements. To do this you use the `MDXProvider` and pass a components object as a prop. Each object key in the components object maps to a `HTML` element name.
To enable you need to specify `providerImportSource: "@mdx-js/react"` in `next.config.js`.
```js
// next.config.js
const withMDX = require('@next/mdx')({
// ...
options: {
providerImportSource: '@mdx-js/react',
},
})
```
Then setup the provider in your page
```jsx
// pages/index.js
......@@ -186,6 +201,8 @@ export default function Post(props) {
}
```
If you use it across the site you may want to add the provider to `_app.js` so all MDX pages pick up the custom element config.
## Helpful Links
- [MDX](https://mdxjs.com)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment