update README

Author: motdotla

README.md

@@ -6,7 +6,9 @@
 >
 > [2 minute tutorial 📺](https://www.youtube.com/watch?v=YtkZR0NFd1g)
 
-### Quickstart
+ 
+
+### Usage
 
 Install it.
 
@@ -69,53 +71,9 @@ s3.getBucketCors({Bucket: process.env.S3_BUCKET}, function(err, data) {})
 * [Deploying](#deploying)
 * [Agents (AS2) 🆕](#agents-as2)
 
-## Usage
-
-<a href="https://www.youtube.com/watch?v=YtkZR0NFd1g">
-<img src="https://img.youtube.com/vi/YtkZR0NFd1g/hqdefault.jpg" alt="how to use dotenv video tutorial" align="right" width="330" />
-<img src="https://simpleicons.vercel.app/youtube/ff0000" alt="youtube/@dotenvorg" align="right" width="24" />
-</a>
-
-Create a `.env` file in the root of your project (if using a monorepo structure like `apps/backend/app.js`, put it in the root of the folder where your `app.js` process runs):
-
-```ini
-S3_BUCKET="YOURS3BUCKET"
-SECRET_KEY="YOURSECRETKEYGOESHERE"
-```
-
-As early as possible in your application, import and configure dotenv:
-
-```javascript
-require('dotenv').config()
-console.log(process.env) // remove this after you've confirmed it is working
-```
-
-.. [or using ES6?](#how-do-i-use-dotenv-with-import)
-
-```javascript
-import 'dotenv/config'
-```
-
-ES6 import if you need to set config options:
-
-```javascript
-import dotenv from 'dotenv'
-
-dotenv.config({ path: '/custom/path/to/.env' })
-```
-
-That's it. `process.env` now has the keys and values you defined in your `.env` file:
-
-```javascript
-require('dotenv').config()
-// or import 'dotenv/config' if you're using ES6
-
-...
-
-s3.getBucketCors({Bucket: process.env.S3_BUCKET}, function(err, data) {})
-```
+## Advanced
 
-### Multiline values
+<details><summary>Multiline Values</summary><br>
 
 If you need multiline variables, for example private keys, those are now supported (`>= v15.0.0`) with line breaks:
 
@@ -133,7 +91,8 @@ Alternatively, you can double quote strings and use the `\n` character:
 PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----\nKh9NV...\n-----END RSA PRIVATE KEY-----\n"
 ```
 
-### Comments
+</details>
+<details><summary>Comments</summary><br>
 
 Comments may be added to your file on their own line or inline:
 
@@ -145,7 +104,10 @@ SECRET_HASH="something-with-a-#-hash"
 
 Comments begin where a `#` exists, so if your value contains a `#` please wrap it in quotes. This is a breaking change from `>= v15.0.0` and on.
 
-### Parsing
+</details>
+
+
+<details><summary>Parsing</summary><br>
 
 The engine which parses the contents of your file containing environment variables is available to use. It accepts a String or Buffer and will return an Object with the parsed keys and values.
 
@@ -156,7 +118,8 @@ const config = dotenv.parse(buf) // will return an object
 console.log(typeof config, config) // object { BASIC : 'basic' }
 ```
 
-### Preload
+</details>
+<details><summary>Preload</summary><br>
 
 > Note: Consider using [`dotenvx`](https://github.com/dotenvx/dotenvx) instead of preloading. I am now doing (and recommending) so.
 >
@@ -184,7 +147,8 @@ $ DOTENV_CONFIG_<OPTION>=value node -r dotenv/config your_script.js
 $ DOTENV_CONFIG_ENCODING=latin1 DOTENV_CONFIG_DEBUG=true node -r dotenv/config your_script.js dotenv_config_path=/custom/path/to/.env
 ```
 
-### Variable Expansion
+</details>
+<details><summary>Variable Expansion</summary><br>
 
 Use [dotenvx](https://github.com/dotenvx/dotenvx) to use variable expansion.
 
@@ -205,7 +169,8 @@ $ dotenvx run --debug -- node index.js
 DATABASE_URL postgres://username@localhost/my_database
 ```
 
-### Command Substitution
+</details>
+<details><summary>Command Substitution</summary><br>
 
 Use [dotenvx](https://github.com/dotenvx/dotenvx) to use command substitution.
 
@@ -225,18 +190,63 @@ $ dotenvx run --debug -- node index.js
 DATABASE_URL postgres://yourusername@localhost/my_database
 ```
 
-### Syncing
+</details>
+<details><summary>Syncing</summary><br>
 
 You need to keep `.env` files in sync between machines, environments, or team members? Use [dotenvx](https://github.com/dotenvx/dotenvx) to encrypt your `.env` files and safely include them in source control. This still subscribes to the twelve-factor app rules by generating a decryption key separate from code.
 
-### Multiple Environments
+</details>
+<details><summary>Multiple Environments</summary><br>
 
 Use [dotenvx](https://github.com/dotenvx/dotenvx) to generate `.env.ci`, `.env.production` files, and more.
 
-### Deploying
+</details>
+
+<details><summary>Deploying</summary><br>
 
 You need to deploy your secrets in a cloud-agnostic manner? Use [dotenvx](https://github.com/dotenvx/dotenvx) to generate a private decryption key that is set on your production server.
 
+</details>
+
+Create a `.env` file in the root of your project (if using a monorepo structure like `apps/backend/app.js`, put it in the root of the folder where your `app.js` process runs):
+
+```ini
+S3_BUCKET="YOURS3BUCKET"
+SECRET_KEY="YOURSECRETKEYGOESHERE"
+```
+
+As early as possible in your application, import and configure dotenv:
+
+```javascript
+require('dotenv').config()
+console.log(process.env) // remove this after you've confirmed it is working
+```
+
+.. [or using ES6?](#how-do-i-use-dotenv-with-import)
+
+```javascript
+import 'dotenv/config'
+```
+
+ES6 import if you need to set config options:
+
+```javascript
+import dotenv from 'dotenv'
+
+dotenv.config({ path: '/custom/path/to/.env' })
+```
+
+That's it. `process.env` now has the keys and values you defined in your `.env` file:
+
+```javascript
+require('dotenv').config()
+// or import 'dotenv/config' if you're using ES6
+
+...
+
+s3.getBucketCors({Bucket: process.env.S3_BUCKET}, function(err, data) {})
+```
+
 &nbsp;
 
 ## Multiple Environments