Shortcode Updates (requires theme update) (linode#5959)

* Updated some of the existing note shortcodes

* Update shortcodes in product docs

* Additional shortcode updates in guides

* Additional updates

* Additional changes

* Fix shortcodes that had an odd number of indent spaces

* Fix some merge conflict syntax that made it into production previously

Co-authored-by: Nathan Melehan <nmelehan@gmail.com>

Author: wildmanonline

docs/guides/_shortguides/all-linodes-kvm-shortguide/index.md

@@ -16,8 +16,6 @@ show_on_rss_feed: false
 aliases: ['/all-linodes-kvm-shortguide/']
 ---
 
-{{< note >}}
-
+{{< note>}}
 This guide mentions Xen architecture. However, all Linode instances now use KVM architecture. This guide may be updated or replaced in the future; or it may be retained for historical purposes.
-
-{{< /note >}}
+{{< /note >}}

docs/guides/_shortguides/email-warning-shortguide/index.md

@@ -16,8 +16,6 @@ show_on_rss_feed: false
 aliases: ['/email-warning-shortguide/']
 ---
 
-{{< disclosure-note "Note About Email at Linode" >}}
-
+{{< note type="secondary" title="Note About Email at Linode" isCollapsible=true >}}
 This guide may involve or result in sending email. In an effort to fight spam, Linode may restrict outbound connections on ports 25, 465, and 587 on Linodes for new accounts created after November 5th, 2019. For more information, please see [Sending Email on Linode](/docs/guides/running-a-mail-server/#sending-email-on-linode).
-
-{{< /disclosure-note >}}
+{{< /note >}}

docs/guides/_shortguides/limited-user-note-shortguide/index.md

@@ -17,9 +17,7 @@ aliases: ['/limited-user-note-shortguide/']
 ---
 
 {{< note >}}
-
 This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you're not familiar with the `sudo` command, visit our [Users and Groups](/docs/guides/linux-users-and-groups/) guide.
 
 All configuration files should be edited with elevated privileges. Remember to include `sudo` before running your text editor.
-
-{{< /note >}}
+{{< /note >}}

docs/guides/akamai/get-started/create-a-simple-microsite/index.md

@@ -69,7 +69,7 @@ To avoid an unexpected bill make sure to delete this Linode Compute Instance onc
 
 1.  Enter required information under the **NodeJS Setup** section. For more information and instructions refer to [Guides - Deploying Node.js through the Linode Marketplace](/docs/products/tools/marketplace/guides/nodejs/).
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 This guide involves configuring DNS settings and SSL certificates for your domain. These steps can be automated during the Marketplace App installation process by providing a Linode [API Token](/docs/products/tools/api/get-started/#create-an-api-token) during setup.
 
 During installation, the API Token is used to generate a domain zone and records using Linode [DNS Manager](/docs/products/networking/dns-manager/). The Node.js Marketplace App then utilizes [certbot](https://certbot.eff.org/) to generate SSL certificates for your domain and subdomain.
@@ -93,7 +93,7 @@ If you plan to utilize Linode DNS Manager, we recommend taking steps now familia
 
 1.  [Verify Marketplace App installation](/docs/products/tools/marketplace/get-started/#verify-installation) before continuing with this guide. It may take several minutes for installation to complete.
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 You can also create a Linode Compute instance using these options:
 
 * Create a new Linux machine and install and set up a custom web server. For more information and instructions, refer to [Creating a Compute Instance](/docs/guides/creating-a-compute-instance/).
@@ -103,7 +103,7 @@ You can also create a Linode Compute instance using these options:
 * To learn how to manually get an SSL certificate for your web server, refer to the [Enabling HTTPS Using Certbot with NGINX](/docs/guides/enabling-https-using-certbot-with-nginx-on-ubuntu) guide.
 {{< /note >}}
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 The steps in this example reference the Linode and Akamai user interfaces. You can also perform these tasks using [Terraform](/docs/guides/how-to-build-your-infrastructure-using-terraform-and-linode/), the management [API](/docs/products/tools/api/get-started/), or [CLI](/docs/products/tools/cli/get-started/).
 {{< /note >}}
 
@@ -175,7 +175,7 @@ server {
     | --------------- | ------------ | --------------- | ---------------------- |
     | `www.test.com`  | TXT          | `_acme-challenge` | **Enter Record Value** |
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 Ensure that there no extra empty spaces when entering the Record Value.
     {{< /note >}}
 
@@ -193,7 +193,7 @@ Ensure that there no extra empty spaces when entering the Record Value.
 
 1.  After you complete the test, remove the line you added to your local hosts file and click **Next**.
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 You can also test with staging IP addresses for your Edge hostname. For example, if your edge hostname is `www.test.com.edgesuite.net`, its staging hostname is `www.test.com.edgesuite-staging.net`.
 
 Run the `nslookup` or `dig` commands on the staging hostname as shown below.
@@ -281,7 +281,7 @@ Before you start, make sure that each of your origin servers has a private IPv4
 
 1.  In the **SSL Certificate** section, paste the PEM-formatted contents of your web server SSL certificate.
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 If using the Node.js Marketplace App, certificate files are located in the `/etc/letsencrypt/live/domain/` directory on your origin servers. Use the contents `fullchain.pem` and `privkey.pem` when configuring your NodeBalancer.
 
 Otherwise, to learn how to get an SSL certificate, refer to the [Enabling HTTPS Using Certbot with NGINX](/docs/guides/enabling-https-using-certbot-with-nginx-on-ubuntu) guide.
@@ -293,7 +293,7 @@ Otherwise, to learn how to get an SSL certificate, refer to the [Enabling HTTPS
 
     ![NodeBalancer Port Configuration](portConfiguration.png "NodeBalancer Port Configuration")
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 To enable [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) for SSL/TLS connections, follow the instructions in the [NodeBalancer SSL Configuration](/docs/products/networking/nodebalancers/guides/ssl-termination/#diffie-hellman-parameters) guide.
 
 If using the Node.js Marketplace app, Diffie-Hellman parameters are located on the Linode origin server in the `/etc/letsencrypt/ssl-dhparams.pem` file by default.
@@ -303,7 +303,7 @@ If using the Node.js Marketplace app, Diffie-Hellman parameters are located on t
 
     ![NodeBalancer Active Health Checks Configuration](activeHealthCheck.png "NodeBalancer Active Health Checks Configuration")
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 Make sure all the origin servers listen to HTTP, not HTTPS, otherwise the HTTP Status option will not work.
     {{< /note >}}
 
@@ -331,7 +331,7 @@ Make sure all the origin servers listen to HTTP, not HTTPS, otherwise the HTTP S
     | ----------------------------- | ------------| ------------------ | ----------- |
     | `test.com`                    | A/AAAA      | `origin-0361ece-www` | 203.0.113.2 |
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 For more information on configuration options, see the [TLS/SSL Termination on NodeBalancers](/docs/products/networking/nodebalancers/guides/ssl-termination/) guide.
 {{< /note >}}
 

docs/guides/applications/big-data/apache-airflow-tutorial-creating-connections-and-variables/index.md

@@ -80,9 +80,9 @@ Using a JSON file to load [Airflow variables](https://airflow.apache.org/docs/st
 dbname
     {{</ output >}}
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 Airflow saves the passwords for connections and any variable values in plain text within the metadata database. See the [A Recommended Workflow for Sensitive Variables](#a-recommended-workflow-for-sensitive-variables) section for ways to keep your variables secure.
-    {{</ note >}}
+    {{< /note >}}
 
 ### Create Your Connection Script
 

docs/guides/applications/big-data/big-data-in-the-linode-cloud-streaming-data-processing-with-apache-storm/index.md

@@ -38,9 +38,9 @@ Some use cases where Storm is a good solution:
 
 This guide explains how to create Storm clusters on the Linode cloud using a set of shell scripts that use Linode's Application Programming Interface (APIs) to programmatically create and configure large clusters. The scripts are all provided by the author of this guide via [GitHub repository](https://github.com/pathbreak/storm-linode). This application stack could also benefit from large amounts of disk space, so consider using our [Block Storage](/docs/products/storage/block-storage/) service with this setup.
 
-{{< caution >}}
+{{< note type="alert" >}}
 External resources are outside of our control, and can be changed and/or modified without our knowledge. Always review code from third party sites yourself before executing.
-{{< /caution >}}
+{{< /note >}}
 
  The deployed architecture will look like this:
 
@@ -136,7 +136,7 @@ export LINODE_KEY=fnxaZ5HMsaImTTRO8SBtg48...
             source ~/storm-linode/api_env_linode.conf
             ~/storm-linode/linode_api.py plans
 
-        {{< note >}}
+        {{< note respectIndent=false >}}
 You only need to run `source` on this file once in a single terminal session, unless you make changes to it.
 {{< /note >}}
 
@@ -153,7 +153,7 @@ You only need to run `source` on this file once in a single terminal session, un
 
         The default value of `124` selects Ubuntu 14.04 LTS 64-bit. If you'd like to use Debian 8 instead, change this value to `140`.
 
-        {{< note >}}
+        {{< note respectIndent=false >}}
 The values represented in this guide are current as of publication, but are subject to change in the future. You can run `~/storm-linode/linode_api.py distributions` to see a list of all available distributions and their values in the API.
 {{< /note >}}
 
@@ -163,7 +163,7 @@ The values represented in this guide are current as of publication, but are subj
     -  `DISABLE_SSH_PASSWORD_AUTHENTICATION`:
         This disables SSH password authentication and allows only key-based SSH authentication for the Cluster Manager Linode. Password authentication is considered less secure, and is hence disabled by default. To enable password authentication, you can change this value to `no`.
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 The options shown in this section are generated by the `linode_api.py` script, and differ slightly from the options shown using the Linode CLI tool. Do not use the Linode CLI tool to configure your Manager Node.
 {{< /note >}}
 
@@ -202,9 +202,9 @@ Match User clustermgrguest
 
         service ssh restart
 
-    {{< caution >}}
+    {{< note type="alert" respectIndent=false >}}
 Since access to the cluster manager provides access to all Storm and Zookeeper clusters and any sensitive data they are processing, its security configuration should be considered critical, and access should be as restrictive as possible.
-{{< /caution >}}
+{{< /note >}}
 
 9.  Log in to the cluster manager Linode as the `root` user, using the public IP address shown when you created it:
 
@@ -298,7 +298,7 @@ When creating an image, you should have `clustermgr` authorization to the Cluste
 
         All nodes of all clusters created from this image will have this distribution. The default value is `124` corresponding to Ubuntu 14.04 LTS 64-bit. For Debian 8 64-bit, change this value to `140`.
 
-        {{< note >}}
+        {{< note respectIndent=false >}}
 The values represented in this guide are current as of publication, but are subject to change in the future. You can run `~/storm-linode/linode_api.py distributions` to see a list of all available distributions and their values in the API.
 {{< /note >}}
 
@@ -430,7 +430,7 @@ The values represented in this guide are current as of publication, but are subj
 
     If the process fails, ensure that you do not already have an existing Linode with the same name in the Linode Manager. If you do, delete it and run the command again, or recreate this image with a different name.
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 During this process, a temporary, short-lived 2GB Linode is created and deleted. This will entail a small cost in your monthly invoice and trigger an event notification email to be sent to the address you have registered with Linode. This is expected behavior.
 {{< /note >}}
 
@@ -539,9 +539,9 @@ When creating a cluster, you should have `clustermgr` authorization to the Clust
 
         Set this value to `false` if the cluster manager node is located in the *same* Linode data center as the cluster nodes. This is the recommended value. Change to `true` **only** if the cluster manager node is located in a *different* Linode data center from the cluster nodes.
 
-        {{< caution >}}
+        {{< note type="alert" respectIndent=false >}}
 It's important to set this correctly to avoid critical cluster creation failures.
-{{< /caution >}}
+{{< /note >}}
 
         <br>
 
@@ -625,7 +625,7 @@ When creating an image, you should have `clustermgr` authorization to the Cluste
 
         All nodes of all clusters created from this image will have this distribution. The default value is `124` corresponding to Ubuntu 14.04 LTS 64-bit. For Debian 8 64-bit, change this value to `140`.
 
-        {{< note >}}
+        {{< note respectIndent=false >}}
 The values represented in this guide are current as of publication, but are subject to change in the future. You can run `~/storm-linode/linode_api.py distributions` to see a list of all available distributions and their values in the API.
 {{< /note >}}
 
@@ -748,7 +748,7 @@ The values represented in this guide are current as of publication, but are subj
 
     If the process fails, ensure that you do not already have an existing Storm image with the same name in the Linode Manager. If you do, delete it and run the command again, or recreate this image with a different name.
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 During this process, a short-lived 2GB Linode is created and deleted. This will entail a small cost in the monthly invoice and trigger an event notification email to be sent to the address you have registered with Linode. This is expected behavior.
 {{< /note >}}
 
@@ -869,9 +869,9 @@ When creating a cluster, you should have `clustermgr` authorization to the Clust
 
         Set this value to `false` if the cluster manager node is located in the *same* Linode data center as the cluster nodes. This is the recommended value and is also the default. Change to `true` **only** if the cluster manager node is located in a *different* Linode data center from the cluster nodes.
 
-        {{< caution >}}
+        {{< note type="alert" respectIndent=false >}}
 It's important to set this correctly to avoid critical cluster creation failures.
-{{< /caution >}}
+{{< /note >}}
 
         <br>
 
@@ -921,7 +921,7 @@ It's important to set this correctly to avoid critical cluster creation failures
 
 This section will explain how to start a Storm cluster. Doing so will also start any Zookeeper clusters on which it depends, so they do not need to be started separately.
 
-{{< note >}}
+{{< note respectIndent=false >}}
 When starting a cluster, you should have `clustermgr` authorization to the Cluster Manager Linode.
 {{< /note >}}
 
@@ -969,7 +969,7 @@ When performing the steps in this section, you should have `clustermgr` authoriz
 
     ![Whitelist entries](storm-user-whitelist-2.png)
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 Any IP address that is being included in the file should be a *public facing IP* address of the network.
 For example, company networks often assign local addresses like 10.x.x.x or 192.x.x.x addresses to employee workstations, which are then NATted to a public IP address while sending requests outside the company network.
 Since the cluster client node is in the Linode cloud outside your company network, it will see monitoring requests as arriving from this public IP address. So it's the public IP address that should be allowed.
@@ -1198,9 +1198,9 @@ A user with only `clustermgrguest` authorization can use `cluster_info.sh` to de
 
 Stopping a Zookeeper cluster cleanly stops the Zookeeper daemon on all nodes, and shuts down all nodes. The cluster can be restarted later. Note that the nodes **will** still incur Linode's hourly charges when stopped.
 
-{{< caution >}}
+{{< note type="alert" >}}
 Do not stop a Zookeeper cluster while any Storm clusters that depend on it are running. This may result in data loss.
-{{< /caution >}}
+{{< /note >}}
 
 To stop a cluster, use the `stop` command:
 
@@ -1210,9 +1210,9 @@ To stop a cluster, use the `stop` command:
 
 Destroying a Zookeeper cluster permanently deletes all nodes of that cluster and their data. Unlike a Linode that is only shut down, destroyed or deleted Linodes no longer incur hourly charges.
 
-{{< caution >}}
+{{< note type="alert" >}}
 Do not destroy a Zookeeper cluster while any Storm clusters that depend on it are running. It may result in data loss.
-{{< /caution >}}
+{{< /note >}}
 
 To destroy a cluster, use the `destroy` command:
 

docs/guides/applications/big-data/how-to-install-and-configure-a-redis-cluster-on-ubuntu-1604/index.md

@@ -47,7 +47,7 @@ Depending on your version of Linux, it may be possible to install Redis through
         sudo apt-get update && sudo apt-get upgrade
         sudo apt install make gcc libc6-dev tcl
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 Alternatively, you can install the "build-essential" meta-package to load the dependencies for Redis:
 
         sudo apt install build-essential tcl
@@ -97,13 +97,13 @@ cluster-config-file nodes-6379.conf
 cluster-node-timeout 15000
 {{< /file >}}
 
-    {{< caution >}}
+    {{< note type="alert" respectIndent=false >}}
 Without taking additional precautions, your Redis nodes may be exposed to the public internet via their respective public IP addresses. This means your nodes may be vulnerable to automated attacks. For more information, see [Redis Security](https://redis.io/topics/security).
 
 To protect your Redis cluster from outside threats, consider utilizing [Cloud Firewalls](/docs/products/networking/cloud-firewall/) or [VLANs](/docs/products/networking/vlans/) to limit access to your cluster Linodes.
 
 When using VLANs, replace `192.0.2.1` with the respective Linode's IPAM address in each configuration file.
-{{< /caution >}}
+{{< /note >}}
 
 3.  In `c_replica.conf`, the configuration is similar except for an update of the port number. `redis-cli` will be used later to configure this into a replica for the appropriate master.
 
@@ -125,7 +125,7 @@ cluster-node-timeout 15000
     |    2   |  6380  |  b_master.conf  | 6379    | a_replica.conf   |
     |    3   |  6381  |  c_master.conf  | 6380    | b_replica.conf   |
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 Each node in the Redis cluster requires that the defined port the port plus 10000 are open. For example, **Server 1** must have TCP ports 6379 and 16379 open for the master node, and TCP ports 6381 and 16381 open for the replica node. Ensure iptables or ufw is configured properly for each server.
 {{< /note >}}
 
@@ -167,7 +167,7 @@ At this point, each Linode hosts two independent master nodes. The Redis install
 
 1.  SSH into **Server 1**, then create a Redis cluster consisting of your three master nodes with the following command:
 
-    {{< note >}}
+    {{< note respectIndent=false >}}
 If utilizing a [VLAN](/docs/products/networking/vlans/get-started/), use each Linode's IPAM address.
 {{< /note >}}