Remove deploy to now button from all examples (vercel#7101)

Author: mcsdevv

examples/amp/README.md

@@ -39,4 +39,4 @@ now
 
 ## The idea behind the example
 
-This example shows how to create AMP pages using Next.js and the experimental AMP feature. It shows a normal page (non-AMP), an AMP only page, and a hybrid AMP page. 
+This example shows how to create AMP pages using Next.js and the experimental AMP feature. It shows a normal page (non-AMP), an AMP only page, and a hybrid AMP page.

examples/custom-server-fastify/README.md

@@ -30,6 +30,7 @@ npm run dev
 yarn
 yarn dev
 ```
+
 Fastify
 Deploy it to the cloud with [now](https://zeit.co/now) ([download](https://zeit.co/download))
 

examples/custom-server-koa/README.md

@@ -45,7 +45,6 @@ Because the Next.js server is just a node.js module you can combine it with any
 
 The example shows a server that serves the component living in `pages/a.js` when the route `/b` is requested and `pages/b.js` when the route `/a` is accessed. This is obviously a non-standard routing strategy. You can see how this custom routing is being made inside `server.js`.
 
-
 ## Side note: Enabling gzip compression
 
 The most common Koa middleware for handling the gzip compression is [compress](https://github.com/koajs/compress), but unfortunately it is currently not compatible with Next.<br>
@@ -54,10 +53,8 @@ The most common Koa middleware for handling the gzip compression is [compress](h
 If you need to enable the gzip compression, the most simple way to do so is by wrapping the express-middleware [compression](https://github.com/expressjs/compression) with [koa-connect](https://github.com/vkurchatkin/koa-connect):
 
 ```javascript
-const compression = require('compression');
-const koaConnect = require('koa-connect');
-
+const compression = require("compression");
+const koaConnect = require("koa-connect");
 
 server.use(koaConnect(compression()));
-
 ```

examples/parameterized-routing/README.md

@@ -33,7 +33,6 @@ yarn dev
 
 See now documentation [here](https://zeit.co/docs/v2/deployments/routes/) and Next.js example [here](https://zeit.co/examples/nextjs/) for info on deploying with [now](https://zeit.co/now) ([download](https://zeit.co/download))
 
-
 ## The idea behind the example
 
 Next.js allows [Custom server and routing](https://github.com/zeit/next.js#custom-server-and-routing) so you can, as we show in this example, parametrize your routes. What we are doing in `server.js` is matching any route with the pattern `/blog/:id` and then passing the id as a parameter to the `pages/blog.js` page.

examples/pass-server-data/README.md

@@ -57,7 +57,7 @@ The server knows whether or not to use next.js to render the route based on the
 
 Take a look at the following files:
 
-* server.js
-* routes/item.js
-* pages/item.js
-* operations/get-item.js
+- server.js
+- routes/item.js
+- pages/item.js
+- operations/get-item.js

examples/progressive-render/README.md

@@ -45,5 +45,5 @@ In that case you can wrap the component in `react-no-ssr` which will only render
 
 This example features:
 
-* An app with a component that must only be rendered in the client
-* A loading component that will be displayed before rendering the client-only component
+- An app with a component that must only be rendered in the client
+- A loading component that will be displayed before rendering the client-only component

examples/shared-modules/README.md

@@ -41,5 +41,5 @@ now
 
 This example features:
 
-* An app with two pages which has a common Counter component
-* That Counter component maintain the counter inside its module. This is used primarily to illustrate that modules get initialized once and their state variables persist in runtime
+- An app with two pages which has a common Counter component
+- That Counter component maintain the counter inside its module. This is used primarily to illustrate that modules get initialized once and their state variables persist in runtime

examples/using-inferno/README.md

@@ -43,4 +43,4 @@ This example uses [Inferno](https://github.com/infernojs/inferno), an insanely f
 
 Here's how we did it:
 
-* Use `next.config.js` to customize our webpack config to support [inferno-compat](https://www.npmjs.com/package/inferno-compat)
+- Use `next.config.js` to customize our webpack config to support [inferno-compat](https://www.npmjs.com/package/inferno-compat)

examples/using-nerv/README.md

@@ -43,4 +43,4 @@ This example uses [Nerv](https://nerv.aotu.io/) instead of React. It's a "blazin
 
 Here's how we did it:
 
-* Use `next.config.js` to customize our webpack config to support [Nerv](https://nerv.aotu.io/)
+- Use `next.config.js` to customize our webpack config to support [Nerv](https://nerv.aotu.io/)

examples/using-preact/README.md

@@ -43,4 +43,4 @@ This example uses [Preact](https://github.com/developit/preact) instead of React
 
 Here's how we did it:
 
-* Use `next.config.js` to customize our webpack config to support [preact-compat](https://github.com/developit/preact-compat)
+- Use `next.config.js` to customize our webpack config to support [preact-compat](https://github.com/developit/preact-compat)

examples/using-router/README.md

@@ -41,5 +41,5 @@ now
 
 This example features:
 
-* An app linking pages using `next/router` instead of `<Link>` component.
-* Access the pathname using `next/router` and render it in a component
+- An app linking pages using `next/router` instead of `<Link>` component.
+- Access the pathname using `next/router` and render it in a component

examples/with-algolia-react-instantsearch/README.md

@@ -22,6 +22,7 @@ cd with-algolia-react-instantsearch
 ```
 
 Set up Algolia:
+
 - create an [algolia](https://www.algolia.com/) account or use this already [configured index](https://community.algolia.com/react-instantsearch/Getting_started.html#before-we-start)
 - update the appId, apikey and indexName you want to search on in components/app.js
 
@@ -42,6 +43,7 @@ now
 ```
 
 ## The idea behind the example
+
 The goal of this example is to illustrate how you can use [Algolia React InstantSearch](https://community.algolia.com/react-instantsearch/) to perform
 your search with a Server-rendered application developed with Next.js. It also illustrates how you
 can keep in sync the Url with the search.

examples/with-apollo-and-redux-saga/README.md

@@ -38,19 +38,26 @@ now
 ```
 
 ## The idea behind the example
+
 In 2.0.0, Apollo Client severs out-of-the-box support for redux in favor of Apollo's client side state management. This example aims to be an amalgamation of the [`with-apollo`](https://github.com/zeit/next.js/tree/master/examples/with-apollo) and [`with-redux-saga`](https://github.com/zeit/next.js/tree/master/examples/with-redux-saga) examples.
 
 Note that you can access the redux store like you normally would using `react-redux`'s `connect`. Here's a quick example:
 
 ```js
 const mapStateToProps = state => ({
-  location: state.form.location,
+  location: state.form.location
 });
 
-export default withReduxSaga(connect(mapStateToProps, null)(Index));
+export default withReduxSaga(
+  connect(
+    mapStateToProps,
+    null
+  )(Index)
+);
 ```
 
 `connect` must go inside `withReduxSaga` otherwise `connect` will not be able to find the store.
 
 ### Note:
-In these *with-apollo* examples, the ```withData()``` HOC must wrap a top-level component from within the ```pages``` directory. Wrapping a child component with the HOC will result in a ```Warning: Failed prop type: The prop 'serverState' is marked as required in 'WithData(Apollo(Component))', but its value is 'undefined'``` error. Down-tree child components will have access to Apollo, and can be wrapped with any other sort of ```graphql()```, ```compose()```, etc HOC's.
+
+In these _with-apollo_ examples, the `withData()` HOC must wrap a top-level component from within the `pages` directory. Wrapping a child component with the HOC will result in a `Warning: Failed prop type: The prop 'serverState' is marked as required in 'WithData(Apollo(Component))', but its value is 'undefined'` error. Down-tree child components will have access to Apollo, and can be wrapped with any other sort of `graphql()`, `compose()`, etc HOC's.

examples/with-apollo-and-redux/README.md

@@ -38,6 +38,7 @@ now
 ```
 
 ## The idea behind the example
+
 This example serves as a conduit if you were using Apollo 1.X with Redux, and are migrating to Apollo 2.x, however, you have chosen not to manage your entire application state within Apollo (`apollo-link-state`).
 
 In 2.0.0, Apollo serves out-of-the-box support for redux in favor of Apollo's state management. This example aims to be an amalgamation of the [`with-apollo`](https://github.com/zeit/next.js/tree/master/examples/with-apollo) and [`with-redux`](https://github.com/zeit/next.js/tree/master/examples/with-redux) examples.
@@ -46,11 +47,17 @@ Note that you can access the redux store like you normally would using `react-re
 
 ```js
 const mapStateToProps = state => ({
-  location: state.form.location,
+  location: state.form.location
 });
 
-export default withRedux(connect(mapStateToProps, null)(Index));
+export default withRedux(
+  connect(
+    mapStateToProps,
+    null
+  )(Index)
+);
 ```
 
 ### Note:
-In these *with-apollo* examples, the ```withData()``` HOC must wrap a top-level component from within the ```pages``` directory. Wrapping a child component with the HOC will result in a ```Warning: Failed prop type: The prop 'serverState' is marked as required in 'WithData(Apollo(Component))', but its value is 'undefined'``` error. Down-tree child components will have access to Apollo, and can be wrapped with any other sort of ```graphql()```, ```compose()```, etc HOC's.
+
+In these _with-apollo_ examples, the `withData()` HOC must wrap a top-level component from within the `pages` directory. Wrapping a child component with the HOC will result in a `Warning: Failed prop type: The prop 'serverState' is marked as required in 'WithData(Apollo(Component))', but its value is 'undefined'` error. Down-tree child components will have access to Apollo, and can be wrapped with any other sort of `graphql()`, `compose()`, etc HOC's.

examples/with-apollo-auth/README.md

@@ -43,13 +43,13 @@ This is an extention of the _[with Apollo](https://github.com/zeit/next.js/tree/
 
 > [Apollo](https://www.apollographql.com/client/) is a GraphQL client that allows you to easily query the exact data you need from a GraphQL server. In addition to fetching and mutating data, Apollo analyzes your queries and their results to construct a client-side cache of your data, which is kept up to date as further queries and mutations are run, fetching more results from the server.
 >
-> In this simple example, we integrate Apollo seamlessly with Next by wrapping our *pages* inside a [higher-order component (HOC)](https://facebook.github.io/react/docs/higher-order-components.html). Using the HOC pattern we're able to pass down a central store of query result data created by Apollo into our React component hierarchy defined inside each page of our Next application.
+> In this simple example, we integrate Apollo seamlessly with Next by wrapping our _pages_ inside a [higher-order component (HOC)](https://facebook.github.io/react/docs/higher-order-components.html). Using the HOC pattern we're able to pass down a central store of query result data created by Apollo into our React component hierarchy defined inside each page of our Next application.
 >
-> On initial page load, while on the server and inside `getInitialProps`, we invoke the Apollo method,  [`getDataFromTree`](https://www.apollographql.com/docs/react/features/server-side-rendering.html#getDataFromTree). This method returns a promise; at the point in which the promise resolves, our Apollo Client store is completely initialized.
+> On initial page load, while on the server and inside `getInitialProps`, we invoke the Apollo method, [`getDataFromTree`](https://www.apollographql.com/docs/react/features/server-side-rendering.html#getDataFromTree). This method returns a promise; at the point in which the promise resolves, our Apollo Client store is completely initialized.
 >
 > This example relies on [graph.cool](https://www.graph.cool) for its GraphQL backend.
 >
-> *Note: If you're interested in integrating the client with your existing Redux store check out the [`with-apollo-and-redux`](https://github.com/zeit/next.js/tree/master/examples/with-apollo-and-redux) example.*
+> _Note: If you're interested in integrating the client with your existing Redux store check out the [`with-apollo-and-redux`](https://github.com/zeit/next.js/tree/master/examples/with-apollo-and-redux) example._
 
 [graph.cool](https://www.graph.cool) can be setup with many different
 [authentication providers](https://www.graph.cool/docs/reference/integrations/overview-seimeish6e/#authentication-providers), the most basic of which is [email-password authentication](https://www.graph.cool/docs/reference/simple-api/user-authentication-eixu9osueb/#email-and-password). Once email-password authentication is enabled for your graph.cool project, you are provided with 2 useful mutations: `createUser` and `signinUser`.
@@ -65,6 +65,6 @@ It is important to note the use of Apollo's `resetStore()` method after signing
 To get this example running locally, you will need to create a graph.cool
 account, and provide [the `project.graphcool` schema](https://github.com/zeit/next.js/blob/master/examples/with-apollo-auth/project.graphcool).
 
-
 ### Note:
-In these *with-apollo* examples, the ```withData()``` HOC must wrap a top-level component from within the ```pages``` directory. Wrapping a child component with the HOC will result in a ```Warning: Failed prop type: The prop 'serverState' is marked as required in 'WithData(Apollo(Component))', but its value is 'undefined'``` error. Down-tree child components will have access to Apollo, and can be wrapped with any other sort of ```graphql()```, ```compose()```, etc HOC's.
+
+In these _with-apollo_ examples, the `withData()` HOC must wrap a top-level component from within the `pages` directory. Wrapping a child component with the HOC will result in a `Warning: Failed prop type: The prop 'serverState' is marked as required in 'WithData(Apollo(Component))', but its value is 'undefined'` error. Down-tree child components will have access to Apollo, and can be wrapped with any other sort of `graphql()`, `compose()`, etc HOC's.

examples/with-apollo/README.md

@@ -45,12 +45,11 @@ now
 
 [Apollo](https://www.apollographql.com/client/) is a GraphQL client that allows you to easily query the exact data you need from a GraphQL server. In addition to fetching and mutating data, Apollo analyzes your queries and their results to construct a client-side cache of your data, which is kept up to date as further queries and mutations are run, fetching more results from the server.
 
-In this simple example, we integrate Apollo seamlessly with Next by wrapping our *pages/_app.js* inside a [higher-order component (HOC)](https://facebook.github.io/react/docs/higher-order-components.html). Using the HOC pattern we're able to pass down a central store of query result data created by Apollo into our React component hierarchy defined inside each page of our Next application.
+In this simple example, we integrate Apollo seamlessly with Next by wrapping our _pages/\_app.js_ inside a [higher-order component (HOC)](https://facebook.github.io/react/docs/higher-order-components.html). Using the HOC pattern we're able to pass down a central store of query result data created by Apollo into our React component hierarchy defined inside each page of our Next application.
 
-On initial page load, while on the server and inside `getInitialProps`, we invoke the Apollo method,  [`getDataFromTree`](https://www.apollographql.com/docs/react/features/server-side-rendering.html#getDataFromTree). This method returns a promise; at the point in which the promise resolves, our Apollo Client store is completely initialized.
+On initial page load, while on the server and inside `getInitialProps`, we invoke the Apollo method, [`getDataFromTree`](https://www.apollographql.com/docs/react/features/server-side-rendering.html#getDataFromTree). This method returns a promise; at the point in which the promise resolves, our Apollo Client store is completely initialized.
 
 This example relies on [graph.cool](https://www.graph.cool) for its GraphQL backend.
 
-
-Note: Do not be alarmed that you see two renders being executed.  Apollo recursively traverses the React render tree looking for Apollo query components. When it has done that, it fetches all these queries and then passes the result to a cache. This cache is then used to render the data on the server side (another React render).
+Note: Do not be alarmed that you see two renders being executed. Apollo recursively traverses the React render tree looking for Apollo query components. When it has done that, it fetches all these queries and then passes the result to a cache. This cache is then used to render the data on the server side (another React render).
 https://www.apollographql.com/docs/react/features/server-side-rendering.html#getDataFromTree

examples/with-app-layout/readme.md

@@ -39,4 +39,4 @@ now
 
 ## The idea behind the example
 
-Shows how to use _app.js to implement a global layout for all pages.
+Shows how to use \_app.js to implement a global layout for all pages.

examples/with-cerebral/README.md

@@ -49,9 +49,9 @@ Declarative CerebralJS:
   getUser,
   {
     success: setUser,
-    error: setError,
+    error: setError
   },
-  setLoading(false),
+  setLoading(false)
 ];
 ```
 

examples/with-context-api/README.md

@@ -37,7 +37,7 @@ Deploy it to the cloud with [now](https://zeit.co/now) ([download](https://zeit.
 now
 ```
 
-## The idea behind the example*
+## The idea behind the example\*
 
 This example shows how to use react context api in our app.
 
@@ -47,5 +47,4 @@ The `pages/index.js` shows how to, from the home page, increment and decrement t
 
 The `pages/about.js` shows how to, from the about page, how to pass an increment value from the about page into the context provider itself.
 
-
-**Based on WesBos example*.
+\*_Based on WesBos example_.

examples/with-custom-babel-config/README.md

@@ -41,8 +41,8 @@ now
 
 This example features:
 
-* An app using proposed [do expressions](https://babeljs.io/docs/plugins/transform-do-expressions/).
-* It uses babel-preset-stage-0, which allows us to use above JavaScript feature.
-* It uses '.babelrc' file in the app directory to add above preset.
+- An app using proposed [do expressions](https://babeljs.io/docs/plugins/transform-do-expressions/).
+- It uses babel-preset-stage-0, which allows us to use above JavaScript feature.
+- It uses '.babelrc' file in the app directory to add above preset.
 
 > Most of the time, when writing a custom `.babelrc` file, you need to add `next/babel` as a preset.

examples/with-docker/README.md

@@ -47,7 +47,7 @@ now --docker -e API_URL="https://example.com"
 
 ## The idea behind the example
 
-This example show how to set custom environment variables for your __docker application__ at runtime.
+This example show how to set custom environment variables for your **docker application** at runtime.
 
 The `dockerfile` is the simplest way to run Next.js app in docker, and the size of output image is `173MB`. However, for an even smaller build, you can do multi-stage builds with `dockerfile.multistage`. The size of output image is `85MB`.
 

examples/with-dotenv/README.md

@@ -43,7 +43,7 @@ This example shows how to inline env vars.
 
 **Please note**:
 
-* It is a bad practice to commit env vars to a repository. Thats why you should normally [gitignore](https://git-scm.com/docs/gitignore) your `.env` file.
-* In this example, as soon as you reference an env var in your code it will be automatically be publicly available and exposed to the client.
-* If you want to have more centralized control of what is exposed to the client check out the example [with-universal-configuration-build-time](../with-universal-configuration-build-time).
-* Env vars are set (inlined) at build time. If you need to configure your app on rutime check out [examples/with-universal-configuration-runtime](../with-universal-configuration-runtime).
+- It is a bad practice to commit env vars to a repository. Thats why you should normally [gitignore](https://git-scm.com/docs/gitignore) your `.env` file.
+- In this example, as soon as you reference an env var in your code it will be automatically be publicly available and exposed to the client.
+- If you want to have more centralized control of what is exposed to the client check out the example [with-universal-configuration-build-time](../with-universal-configuration-build-time).
+- Env vars are set (inlined) at build time. If you need to configure your app on rutime check out [examples/with-universal-configuration-runtime](../with-universal-configuration-runtime).