Remove unsupported examples (#26075)

Co-authored-by: JJ Kasper <jj@jjsweb.site>
vercel · Jun 14, 2021 · de08b1f · de08b1f
1 parent 8fd5d92
commit de08b1f
Show file tree

Hide file tree

Showing 45 changed files with 31 additions and 503 deletions.
diff --git a/errors/url-deprecated.md b/errors/url-deprecated.md
@@ -10,7 +10,7 @@ The reason this is going away is that we want to make things very predictable an
 
 #### Possible Ways to Fix It
 
-https://github.com/zeit/next-codemod#url-to-withrouter
+https://nextjs.org/docs/advanced-features/codemods#url-to-withrouter
 
 Since Next 5 we provide a way to explicitly inject the Next.js router object into pages and all their descending components.
 The `router` property that is injected will hold the same values as `url`, like `pathname`, `asPath`, and `query`.
@@ -33,4 +33,4 @@ export default withRouter(Page)
 
 We provide a codemod (a code to code transformation) to automatically change the `url` property usages to `withRouter`.
 
-You can find this codemod and instructions on how to run it here: https://github.com/zeit/next-codemod#url-to-withrouter
+You can find this codemod and instructions on how to run it here: https://nextjs.org/docs/advanced-features/codemods#url-to-withrouter
diff --git a/examples/cms-agilitycms/lib/constants.js b/examples/cms-agilitycms/lib/constants.js
@@ -4,4 +4,4 @@ export const CMS_URL = 'https://www.agilitycms.com'
 export const CMS_LANG = 'en-us'
 export const CMS_CHANNEL = 'website'
 export const HOME_OG_IMAGE_URL =
-  'https://og-image.vercel.app/Next.js%20Blog%20Example%20with%20**Agility%20CMS**.png?theme=light&md=1&fontSize=75px&images=https%3A%2F%2Fassets.zeit.co%2Fimage%2Fupload%2Ffront%2Fassets%2Fdesign%2Fnextjs-black-logo.svg&images=https%3A%2F%2Fcdn.agilitycms.com%2Fcontent-manager%2Fimages%2Flogos%2F3d69eddf6f00b8824feb126d9ac2bed3ec6e85c0.png&widths=undefined&widths=350&heights=200&heights=auto'
+  'https://og-image.vercel.app/Next.js%20Blog%20Example%20with%20**Agility%20CMS**.png?theme=light&md=1&fontSize=75px&images=https%3A%2F%2Fassets.vercel.com%2Fimage%2Fupload%2Ffront%2Fassets%2Fdesign%2Fnextjs-black-logo.svg&images=https%3A%2F%2Fcdn.agilitycms.com%2Fcontent-manager%2Fimages%2Flogos%2F3d69eddf6f00b8824feb126d9ac2bed3ec6e85c0.png&widths=undefined&widths=350&heights=200&heights=auto'
diff --git a/examples/cms-ghost/components/alert.js b/examples/cms-ghost/components/alert.js
@@ -27,7 +27,7 @@ export default function Alert({ preview }) {
             <>
               The source code for this blog is{' '}
               <a
-                href={`https://github.com/zeit/next.js/tree/canary/examples/${EXAMPLE_PATH}`}
+                href={`https://github.com/vercel/next.js/tree/canary/examples/${EXAMPLE_PATH}`}
                 className="underline hover:text-success duration-200 transition-colors"
               >
                 available on GitHub

diff --git a/examples/cms-ghost/components/footer.js b/examples/cms-ghost/components/footer.js
@@ -17,7 +17,7 @@ export default function Footer() {
               Read Documentation
             </a>
             <a
-              href={`https://github.com/zeit/next.js/tree/canary/examples/${EXAMPLE_PATH}`}
+              href={`https://github.com/vercel/next.js/tree/canary/examples/${EXAMPLE_PATH}`}
               className="mx-3 font-bold hover:underline"
             >
               View on GitHub

diff --git a/examples/with-ant-design-mobile/.babelrc b/examples/with-ant-design-mobile/.babelrc
diff --git a/examples/with-ant-design-mobile/.gitignore b/examples/with-ant-design-mobile/.gitignore
diff --git a/examples/with-ant-design-mobile/README.md b/examples/with-ant-design-mobile/README.md
diff --git a/examples/with-ant-design-mobile/components/Layout.js b/examples/with-ant-design-mobile/components/Layout.js
diff --git a/examples/with-ant-design-mobile/next.config.js b/examples/with-ant-design-mobile/next.config.js
diff --git a/examples/with-ant-design-mobile/package.json b/examples/with-ant-design-mobile/package.json
diff --git a/examples/with-ant-design-mobile/pages/_app.js b/examples/with-ant-design-mobile/pages/_app.js
diff --git a/examples/with-ant-design-mobile/pages/about.js b/examples/with-ant-design-mobile/pages/about.js
diff --git a/examples/with-ant-design-mobile/pages/index.js b/examples/with-ant-design-mobile/pages/index.js
diff --git a/examples/with-aphrodite/README.md b/examples/with-aphrodite/README.md
@@ -1,6 +1,6 @@
 # Example app with aphrodite
 
-This example features how to use a different styling solution than [styled-jsx](https://github.com/zeit/styled-jsx) that also supports universal styles. That means we can serve the required styles for the first render within the HTML and then load the rest in the client. In this case we are using [Aphrodite](https://github.com/Khan/aphrodite/).
+This example features how to use a different styling solution than [styled-jsx](https://github.com/vercel/styled-jsx) that also supports universal styles. That means we can serve the required styles for the first render within the HTML and then load the rest in the client. In this case we are using [Aphrodite](https://github.com/Khan/aphrodite/).
 
 For this purpose we are extending the `<Document />` and injecting the server side rendered styles into the `<head>`.
 

diff --git a/examples/with-astroturf/.gitignore b/examples/with-astroturf/.gitignore
diff --git a/examples/with-astroturf/README.md b/examples/with-astroturf/README.md
diff --git a/examples/with-astroturf/next.config.js b/examples/with-astroturf/next.config.js
diff --git a/examples/with-astroturf/package.json b/examples/with-astroturf/package.json
diff --git a/examples/with-astroturf/pages/index.js b/examples/with-astroturf/pages/index.js
diff --git a/examples/with-astroturf/postcss.config.js b/examples/with-astroturf/postcss.config.js
diff --git a/examples/with-compiled-css/README.md b/examples/with-compiled-css/README.md
@@ -1,6 +1,6 @@
 # Example app with [Compiled](https://github.com/atlassian-labs/compiled) (CSS-in-JS)
 
-This example features how to use [Compiled](https://github.com/atlassian-labs/compiled) as the build time CSS-in-JS styling solution instead of [styled-jsx](https://github.com/zeit/styled-jsx).
+This example features how to use [Compiled](https://github.com/atlassian-labs/compiled) as the build time CSS-in-JS styling solution instead of [styled-jsx](https://github.com/vercel/styled-jsx).
 
 ## Preview
 

diff --git a/examples/with-cxs/README.md b/examples/with-cxs/README.md
@@ -1,6 +1,6 @@
 # Example app with cxs
 
-This example shows how to use a different styling solution than [styled-jsx](https://github.com/zeit/styled-jsx) that also supports universal styles. That means we can serve the required styles for the first render within the HTML and then load the rest in the client. In this case we are using [cxs](https://github.com/jxnblk/cxs/).
+This example shows how to use a different styling solution than [styled-jsx](https://github.com/vercel/styled-jsx) that also supports universal styles. That means we can serve the required styles for the first render within the HTML and then load the rest in the client. In this case we are using [cxs](https://github.com/jxnblk/cxs/).
 
 For this purpose we are extending the `<Document />` and injecting the server side rendered styles into the `<head>`.
 

diff --git a/examples/with-fela/README.md b/examples/with-fela/README.md
@@ -1,6 +1,6 @@
 # Example app with Fela
 
-This example features how to use a different styling solution than [styled-jsx](https://github.com/zeit/styled-jsx) that also supports universal styles. That means we can serve the required styles for the first render within the HTML and then load the rest in the client. In this case we are using [fela](https://github.com/rofrischmann/fela).
+This example features how to use a different styling solution than [styled-jsx](https://github.com/vercel/styled-jsx) that also supports universal styles. That means we can serve the required styles for the first render within the HTML and then load the rest in the client. In this case we are using [fela](https://github.com/rofrischmann/fela).
 
 For this purpose we are extending the `<Document />` and injecting the server side rendered styles into the `<head>`.