archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: add note that contentlayer is unmaintained (#59927)

Browse source 
Co-authored-by: Lee Robinson <me@leerob.io>
This commit is contained in:
Shreyans Jain 2023-12-27 22:39:38 +05:30 committed by GitHub
parent f8ba588ce4
commit 5f2d7b691f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/02-app/01-building-your-application/07-configuring/05-mdx.mdx
View file

@ -130,12 +130,7 @@ Navigating to the `/my-mdx-page` route should display your rendered MDX.
## Remote MDX
If your markdown or MDX files or content lives _somewhere else_, you can fetch it dynamically on the server. This is useful for content stored in a separate local folder, CMS, database, or anywhere else.
There are two popular community packages for fetching MDX content:
- [`next-mdx-remote`](https://github.com/hashicorp/next-mdx-remote#react-server-components-rsc--nextjs-app-directory-support)
- [`contentlayer`](https://www.contentlayer.dev/)
If your markdown or MDX files or content lives _somewhere else_, you can fetch it dynamically on the server. This is useful for content stored in a separate local folder, CMS, database, or anywhere else. A popular community packages for this use is [`next-mdx-remote`](https://github.com/hashicorp/next-mdx-remote#react-server-components-rsc--nextjs-app-directory-support).
> **Good to know**: Please proceed with caution. MDX compiles to JavaScript and is executed on the server. You should only fetch MDX content from a trusted source, otherwise this can lead to remote code execution (RCE).