Remove more examples (vercel#89709)

Removing examples that we are not using, or maintaining anymore.

Author: icyJoseph

docs/01-app/02-guides/mdx.mdx

@@ -747,93 +747,6 @@ export default withMDX(nextConfig)
 >
 > remark and rehype plugins without serializable options cannot be used yet with [Turbopack](/docs/app/api-reference/turbopack), because JavaScript functions can't be passed to Rust.
 
-## Remote MDX
-
-If your MDX files or content lives _somewhere else_, you can fetch it dynamically on the server. This is useful for content stored in a CMS, database, or anywhere else. A community package for this use is [`next-mdx-remote-client`](https://github.com/ipikuka/next-mdx-remote-client?tab=readme-ov-file#the-part-associated-with-nextjs-app-router).
-
-> **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).
-
-The following example uses `next-mdx-remote-client`:
-
-<AppOnly>
-
-```tsx filename="app/mdx-page-remote/page.tsx" switcher
-import { MDXRemote } from 'next-mdx-remote-client/rsc'
-
-export default async function RemoteMdxPage() {
-  // MDX text - can be from a database, CMS, fetch, anywhere...
-  const res = await fetch('https://...')
-  const markdown = await res.text()
-  return <MDXRemote source={markdown} />
-}
-```
-
-```jsx filename="app/mdx-page-remote/page.js" switcher
-import { MDXRemote } from 'next-mdx-remote-client/rsc'
-
-export default async function RemoteMdxPage() {
-  // MDX text - can be from a database, CMS, fetch, anywhere...
-  const res = await fetch('https://...')
-  const markdown = await res.text()
-  return <MDXRemote source={markdown} />
-}
-```
-
-</AppOnly>
-
-<PagesOnly>
-
-```tsx filename="pages/mdx-page-remote.tsx" switcher
-import {
-  serialize,
-  type SerializeResult,
-} from 'next-mdx-remote-client/serialize'
-import { MDXClient } from 'next-mdx-remote-client'
-
-type Props = {
-  mdxSource: SerializeResult
-}
-
-export default function RemoteMdxPage({ mdxSource }: Props) {
-  if ('error' in mdxSource) {
-    // either render error UI or throw `mdxSource.error`
-  }
-  return <MDXClient {...mdxSource} />
-}
-
-export async function getStaticProps() {
-  // MDX text - can be from a database, CMS, fetch, anywhere...
-  const res = await fetch('https:...')
-  const mdxText = await res.text()
-  const mdxSource = await serialize({ source: mdxText })
-  return { props: { mdxSource } }
-}
-```
-
-```jsx filename="pages/mdx-page-remote.js" switcher
-import { serialize } from 'next-mdx-remote-client/serialize'
-import { MDXClient } from 'next-mdx-remote-client'
-
-export default function RemoteMdxPage({ mdxSource }) {
-  if ('error' in mdxSource) {
-    // either render error UI or throw `mdxSource.error`
-  }
-  return <MDXClient {...mdxSource} />
-}
-
-export async function getStaticProps() {
-  // MDX text - can be from a database, CMS, fetch, anywhere...
-  const res = await fetch('https:...')
-  const mdxText = await res.text()
-  const mdxSource = await serialize({ source: mdxText })
-  return { props: { mdxSource } }
-}
-```
-
-</PagesOnly>
-
-Navigating to the `/mdx-page-remote` route should display your rendered MDX.
-
 ## Deep Dive: How do you transform markdown into HTML?
 
 React does not natively understand markdown. The markdown plaintext needs to first be transformed into HTML. This can be accomplished with `remark` and `rehype`.