README updates for the main repo, and a light overview on the docs su…

…bdir (segmentio#1202)

* README updates for the main repo, and a light overview on the docs subdir

* One more fixup

README.md

@@ -21,9 +21,9 @@
 - [Documentation](https://evergreen.segment.com/)
 - [GitHub Discussions](https://github.com/segmentio/evergreen/discussions)
 
-## Evergreen v4 to v5 Migration guide
+## Evergreen v5 to v6 Migration guide
 
-Evergreen v4 to v5 [migration guide](https://evergreen.segment.com/get-started/v5-migration-guide)
+Evergreen v5 to v6 [migration guide](https://evergreen.segment.com/introduction/v6-migration-guide)
 
 ## Install and use components
 
@@ -42,10 +42,7 @@ import React from 'react'
 import ReactDOM from 'react-dom'
 import { Button } from 'evergreen-ui'
 
-ReactDOM.render(
- <Button>I am using 🌲 Evergreen!</Button>,
- document.getElementById('root')
-)
+ReactDOM.render(<Button>I am using 🌲 Evergreen!</Button>, document.getElementById('root'))
 ```
 
 ## Core values of 🌲 Evergreen
@@ -61,9 +58,7 @@ ReactDOM.render(
 
 ### Theming support?
 
-Evergreen v5 supports theming partially. It is still complex to theme Evergreen. We have done exploratory work to make theming more powerful and accessible, and hope to release a new theming api in Evergreen v6.
-
-See these [docs](https://evergreen.segment.com/get-started/theming/) for more information regarding theming in Evergreen.
+Evergreen supports a robust theming layer out of the box. You can check out [these docs](https://evergreen.segment.com/introduction/theming) for more information regarding theming in Evergreen.
 
 ### How does Server Side Rendering (SSR) work?
 
@@ -113,7 +108,7 @@ $ yarn install
 $ yarn dev
 ```
 
-Now you can visit `http:https://localhost:8000/` in your browser.
+Now you can visit `http:https://localhost:3000/` in your browser.
 
 Documentation code is under the `docs` directory. A big portion of these docs are written in MDX, if you've never used MDX before, check out these [docs](https://mdxjs.com/getting-started).
 
@@ -218,4 +213,4 @@ Please respect our [Code of Conduct](.github/CODE_OF_CONDUCT.md), in short:
 Evergreen is released under the MIT license.
 The BlueprintJS icons are licensed under a [custom Apache 2.0 license](https://github.com/palantir/blueprint/blob/develop/LICENSE).
 
-Copyright © 2017 Segment.io, Inc.
+Copyright © 2021 Segment.io, Inc.

docs/README.md

@@ -1,41 +1,27 @@
-# TypeScript Next.js example
+# Evergreen Docs
 
-This is a really simple project that shows the usage of Next.js with TypeScript.
+The following gives some information about getting the Evergreen docs site up and running locally.
 
-## Deploy your own
+# Spinning up the dev server
 
-Deploy the example using [Vercel](https://vercel.com?utm_source=github&utm_medium=readme&utm_campaign=next-example):
+To get started locally, run the following commands:
 
-[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/with-typescript&project-name=with-typescript&repository-name=with-typescript)
-
-## How to use it?
-
-Execute [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app) with [npm](https://docs.npmjs.com/cli/init) or [Yarn](https://yarnpkg.com/lang/en/docs/cli/create/) to bootstrap the example:
-
-```bash
-npx create-next-app --example with-typescript with-typescript-app
-# or
-yarn create next-app --example with-typescript with-typescript-app
+```
+$ (docs): yarn install
+$ (docs): yarn dev
 ```
 
-Deploy it to the cloud with [Vercel](https://vercel.com/new?utm_source=github&utm_medium=readme&utm_campaign=next-example) ([Documentation](https://nextjs.org/docs/deployment)).
-
-## Notes
-
-This example shows how to integrate the TypeScript type system into Next.js. Since TypeScript is supported out of the box with Next.js, all we have to do is to install TypeScript.
+Then, navigate to your browser and go to: `localhost:3000`.
 
-```
-npm install --save-dev typescript
-```
+# Adding a new documentation page
 
-To enable TypeScript's features, we install the type declarations for React and Node.
+Add an entry under the corresponding header in `IA.ts` - you can think of this as the "database" for all status relating to Evergreen components and documentation.
 
-```
-npm install --save-dev @types/react @types/react-dom @types/node
-```
+From there, the directory structure in `docs/documentation/` contains the `.mdx` files which mirror the route structure for the docs site.
 
-When we run `next dev` the next time, Next.js will start looking for any `.ts` or `.tsx` files in our project and builds it. It even automatically creates a `tsconfig.json` file for our project with the recommended settings.
+Any thumbnail images or static assets should be added in the `public/` directory, as they'll be picked up by Next.js.
 
-Next.js has built-in TypeScript declarations, so we'll get autocompletion for Next.js' modules straight away.
+# A note about hot-reloading / fast-refresh
 
-A `type-check` script is also added to `package.json`, which runs TypeScript's `tsc` CLI in `noEmit` mode to run type-checking separately. You can then include this, for example, in your `test` scripts.
+Changes made to any of the UI components that make up `docs/` (i.e. anything with a `ts` or `tsx` extension) will be picked up by Next.js automatically.
+However, if you make changes to any `.mdx`, you should refresh the page that you're looking at.