docs: remove old links for examples (vercel#57891)

Co-authored-by: Lee Robinson <[email protected]>
agustints · Jan 6, 2024 · 53cbe81 · 53cbe81
1 parent 3f5fd5f
commit 53cbe81
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 23 deletions.
diff --git a/docs/02-app/01-building-your-application/05-styling/03-css-in-js.mdx b/docs/02-app/01-building-your-application/05-styling/03-css-in-js.mdx
@@ -259,10 +259,8 @@ export default function RootLayout({ children }) {
 - [Styled Components](https://github.com/vercel/next.js/tree/canary/examples/with-styled-components)
 - [Emotion](https://github.com/vercel/next.js/tree/canary/examples/with-emotion)
 - [Linaria](https://github.com/vercel/next.js/tree/canary/examples/with-linaria)
-- [Tailwind CSS + Emotion](https://github.com/vercel/next.js/tree/canary/examples/with-tailwindcss-emotion)
 - [Styletron](https://github.com/vercel/next.js/tree/canary/examples/with-styletron)
 - [Cxs](https://github.com/vercel/next.js/tree/canary/examples/with-cxs)
-- [Aphrodite](https://github.com/vercel/next.js/tree/canary/examples/with-aphrodite)
 - [Fela](https://github.com/vercel/next.js/tree/canary/examples/with-fela)
 - [Stitches](https://github.com/vercel/next.js/tree/canary/examples/with-stitches)
 

diff --git a/docs/02-app/02-api-reference/05-next-config-js/env.mdx b/docs/02-app/02-api-reference/05-next-config-js/env.mdx
@@ -17,13 +17,6 @@ description: Learn to add and access environment variables in your Next.js appli
 
 </PagesOnly>
 
-<details>
-  <summary>Examples</summary>
-
-- [With env](https://github.com/vercel/next.js/tree/canary/examples/with-env-from-next-config-js)
-
-</details>
-
 <AppOnly>
 
 > **Good to know**: environment variables specified in this way will **always** be included in the JavaScript bundle, prefixing the environment variable name with `NEXT_PUBLIC_` only has an effect when specifying them [through the environment or .env files](/docs/app/building-your-application/configuring/environment-variables).

diff --git a/.../03-pages/01-building-your-application/01-routing/03-linking-and-navigating.mdx b/.../03-pages/01-building-your-application/01-routing/03-linking-and-navigating.mdx
@@ -110,13 +110,6 @@ In general we recommend using [`useRouter`](/docs/pages/api-reference/functions/
 
 ## Imperative Routing
 
-<details>
-  <summary>Examples</summary>
-
-- [Using Router](https://github.com/vercel/next.js/tree/canary/examples/using-router)
-
-</details>
-
 [`next/link`](/docs/pages/api-reference/components/link) should be able to cover most of your routing needs, but you can also do client-side navigations without it, take a look at the [documentation for `next/router`](/docs/pages/api-reference/functions/use-router).
 
 The following example shows how to do basic page navigations with [`useRouter`](/docs/pages/api-reference/functions/use-router):

diff --git a/docs/03-pages/02-api-reference/02-functions/use-router.mdx b/docs/03-pages/02-api-reference/02-functions/use-router.mdx
@@ -54,13 +54,6 @@ The following methods are included inside `router`:
 
 ### router.push
 
-<details>
-  <summary>Examples</summary>
-
-- [Using Router](https://github.com/vercel/next.js/tree/canary/examples/using-router)
-
-</details>
-
 Handles client-side transitions, this method is useful for cases where [`next/link`](/docs/pages/api-reference/components/link) is not enough.
 
 ```js