update links to work with netlify

_articles/send/about-send.md

@@ -10,11 +10,11 @@ order: "01"
 
 ## What is Send?
 
-Bitwarden Send is a secure and ephemeral way to transmit sensitive information to **anyone**. Sends can include plaintext or file attachments up to 500 MB (100 MB if creating from Mobile). Every Send is assigned a randomly generated and secure link, which can be [shared with anyone]({% link _articles/send/receive-send.md %}) (including those who *do not* have Bitwarden accounts) via text, email, or whatever communication channel you prefer. Every Send is:
+Bitwarden Send is a secure and ephemeral way to transmit sensitive information to **anyone**. Sends can include plaintext or file attachments up to 500 MB (100 MB if creating from Mobile). Every Send is assigned a randomly generated and secure link, which can be [shared with anyone]({{site.baseurl}}/receive-send/) (including those who *do not* have Bitwarden accounts) via text, email, or whatever communication channel you prefer. Every Send is:
 
 - **End-to-end Encrypted**: Data in a Send is [encrypted]({{site.baseurl}}/send-encryption/#send-encryption) on creation, and only [decrypted]({{site.baseurl}}/send-encryption/#send-decryption) when a recipient opens the Send link. The contents of a Send are stored **encrypted** in Bitwarden systems, just like a traditional Vault item. The link generated for each send doesn't contain any data related to the Send's contents, so it's safe to share over intermediary communications services without exposing information to Bitwarden or any used intermediary services.
 
-- **Dynamically Ephemeral**: Sends are designed for ephemeral sharing, so every [Send that you create]({% link _articles/send/create-send.md %}) will have a specified [lifespan]({% link _articles/send/send-lifespan.md %}) (*max 31 days*) that can be configured using pre-set options or a custom timestamp for down-to-the-minute specification. When its deletion date is reached, the Send and its contents will be completely purged from Bitwarden systems. Using additional options like [Expiration Date]({{site.baseurl}}/send-lifespan/#expiration-date) and [Maximum Access Count]({{site.baseurl}}/send-lifespan/#maximum-access-count), you can ensure that access to recipients is terminated according to your needs.
+- **Dynamically Ephemeral**: Sends are designed for ephemeral sharing, so every [Send that you create]({{site.baseurl}}/create-send/) will have a specified [lifespan]({{site.baseurl}}/send-lifespan/) (*max 31 days*) that can be configured using pre-set options or a custom timestamp for down-to-the-minute specification. When its deletion date is reached, the Send and its contents will be completely purged from Bitwarden systems. Using additional options like [Expiration Date]({{site.baseurl}}/send-lifespan/#expiration-date) and [Maximum Access Count]({{site.baseurl}}/send-lifespan/#maximum-access-count), you can ensure that access to recipients is terminated according to your needs.
 
 - **Customizably Private**: Protect the contents of your Send by optionally [configuring a password]({{site.baseurl}}/send-privacy/#send-passwords) for access or [hiding your email address from recipients]({{site.baseurl}}/send-privacy/#hide-email). For text Sends, you can also optionally [require users to toggle visibility]({{site.baseurl}}/send-privacy/#hide-text) to prevent exposure to unintentional onlookers.
 
@@ -28,7 +28,7 @@ Sends are created, edited, managed, and deleted from the **Send** view in any Bi
 
 Using Bitwarden Send is a simple two-step process:
 
-1. [Create your Send]({% link _articles/send/create-send.md %}), setting whichever [lifespan options]({% link _articles/send/send-lifespan.md %}) and [privacy options]({% link _articles/send/send-privacy.md %}) are required to fit your sharing needs.
+1. [Create your Send]({{site.baseurl}}/create-send/), setting whichever [lifespan options]({{site.baseurl}}/send-lifespan/) and [privacy options]({{site.baseurl}}/send-privacy/) are required to fit your sharing needs.[Create your Send]({{site.baseurl}}/create-send/)
 2. Share the Send link with the [intended recipients]({% link _articles/send/receive-send.md %}), using whatever communication channel you prefer.
 
-As the Sender, we recommend that you keep track of your Send's [configured lifespan]({% link _articles/send/send-lifespan.md %}). To make that as easy as possible, Sends in your Send view will display [a set of status icons]({{site.baseurl}}/send-faqs/#q-what-do-the-icons-next-to-my-sends-indicate) whenever a lifespan event (for example, expiration) has occurred.
+As the Sender, we recommend that you keep track of your Send's [configured lifespan]({{site.baseurl}}/send-lifespan/). To make that as easy as possible, Sends in your Send view will display [a set of status icons]({{site.baseurl}}/send-faqs/#q-what-do-the-icons-next-to-my-sends-indicate) whenever a lifespan event (for example, expiration) has occurred.

_articles/send/create-send.md

@@ -130,7 +130,7 @@ Complete the following steps to create a new Send from a Bitwarden Desktop App:
 
 1. Select the {% icon fa-paper-plane %} **Send** tab located at the bottom of the left-most column in your Desktop App.
 
-   The center column will list all Sends that haven't reached their [deletion date]({% link _articles/send/send-lifespan.md %}). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by selecting one of the available **Types** from the left-most column.
+   The center column will list all Sends that haven't reached their [deletion date]({{site.baseurl}}/send-lifespan/). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by selecting one of the available **Types** from the left-most column.
 2. To start creating a new Send, select the {% icon fa-plus %} **Add** icon in at the bottom of the center column.
 
     {% image send/send-desktop-add.png Send view in a Desktop App %}
@@ -139,7 +139,7 @@ Complete the following steps to create a new Send from a Bitwarden Desktop App:
    - **Name**: Specify an identifiable, meaningful name for this Send.
    - **Type**: Specify whether this Send will be **Text** or a **File**:
 
-     | **Text** | Type or paste the desired text into the input box. Toggle the **When accessing the send, hide text by default** option to require recipients to [toggle visibility]({% link _articles/send/send-privacy.md %}) when they open a Send.|
+     | **Text** | Type or paste the desired text into the input box. Toggle the **When accessing the send, hide text by default** option to require recipients to [toggle visibility]({{site.baseurl}}/send-privacy/) when they open a Send.|
      | **File** | Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 500 MB (100 MB on Mobile). (**Requires Premium** & Verified Email)|
 
      By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send.
@@ -175,7 +175,7 @@ Complete the following steps to create a new Send from Bitwarden Mobile App:
 
 1. Tap the {% icon fa-paper-plane %} **Send** tab located at the bottom of your screen.
 
-   This view will list all Sends that haven't reached their [deletion date]({% link _articles/send/send-lifespan.md %}). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by tapping one of the available **Types**.
+   This view will list all Sends that haven't reached their [deletion date]({{site.baseurl}}/send-lifespan/). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by tapping one of the available **Types**.
 2. To start creating a new Send, tap the {% icon fa-plus %} **Add** icon:
 
    {% image send/send-mobile.png Send View on iOS and Android%}
@@ -184,7 +184,7 @@ Complete the following steps to create a new Send from Bitwarden Mobile App:
 
    - **Type**: Specify whether this Send will be **Text** or a **File**:
 
-     |**Text** | Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({% link _articles/send/send-privacy.md %}) when they open a Send.|
+     |**Text** | Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({{site.baseurl}}/send-privacy/) when they open a Send.|
      |**File** | Tap the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB (500 MB on other clients). (**Requires Premium** & Verified Email)|
 
    - **Name**: Specify an identifiable, meaningful name for this Send.
@@ -231,7 +231,7 @@ To create a simple file Send with a [deletion date]({{site.baseurl}}s/send-lifes
 bw send -n "My File Send" - d 14 -f /Users/myaccount/Documents/my_file.pdf
 ```
 
-The Bitwarden CLI is a fully-featured and powerful tool. We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article to learn more.
+The Bitwarden CLI is a fully-featured and powerful tool. We recommend reading the [Send from CLI]({{site.baseurl}}/send-cli/) article to learn more.
 
 {% endcapture %}
 {{ cli_info | markdownify}}

_articles/send/receive-send.md

@@ -17,7 +17,7 @@ These links can be opened in any modern web browser, and will open a simple no-n
 
 {% image send/received-send.png A received Send%}
 
-Depending on the [options configured]({% link _articles/send/create-send.md %}) by the Sender, the recipient of a Send may be required to:
+Depending on the [options configured]({{site.baseurl}}/create-send/) by the Sender, the recipient of a Send may be required to:
 
 - Enter a Password to access the contents of the Send.
 - Manually toggle visibility on a hidden-text Send.
@@ -43,6 +43,6 @@ Taking the above measures to ensure the trustworthiness of a hidden-email Send a
 
 ## Deleted, Expired, and Disabled Sends
 
-When a Send has [been deleted, expired, or disabled]({% link _articles/send/send-lifespan.md %}), recipients who attempt to use the generated Send link will be shown a screen that reports the Send does not exist or is no longer available:
+When a Send has [been deleted, expired, or disabled]({{site.baseurl}}/send-lifespan/), recipients who attempt to use the generated Send link will be shown a screen that reports the Send does not exist or is no longer available:
 
 {% image send/send-unavailable.png A deleted, expired, or disabled Send %}

_articles/send/send-cli.md

@@ -8,7 +8,7 @@ tags: [bitwarden send, send, cli]
 order: "06"
 ---
 
-Bitwarden Send is available as a set of fully-featured CLI commands. This article documents the breadth of `bw send` commands, however Send **is not a separate tool** from the Bitwarden Command-line Interface (CLI). Therefore, many of the commands, options, and concepts in the [CLI documentation]({% link _articles/miscellaneous/cli.md %}) are relevant here.
+Bitwarden Send is available as a set of fully-featured CLI commands. This article documents the breadth of `bw send` commands, however Send **is not a separate tool** from the Bitwarden Command-line Interface (CLI). Therefore, many of the commands, options, and concepts in the [CLI documentation]({{site.baseurl}}/cli/) are relevant here.
 
 {% image send/send-cli.png Send's --help text %}
 
@@ -98,7 +98,7 @@ The `get` command will retrieve a Send owned by you and output it as a JSON obje
 bw send get [options] <id / string>
 ```
 
-If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
+If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({{site.baseurl}}/cli/).
 
 **Options:**
 
@@ -143,7 +143,7 @@ The `list` command will list all Sends owned by you and output them as JSON:
 bw send list [options]
 ```
 
-If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
+If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({{site.baseurl}}/cli/).
 
 **Options:**
 

_articles/send/send-encryption.md

@@ -10,7 +10,7 @@ order: "07"
 
 ## Send Encryption
 
-Sends are a secure and ephemeral mechanism for transmitting sensitive information to anyone, include plaintext and files. As the [About Send]({% link _articles/send/about-send.md %}) article notes, Sends are **end-to-end encrypted**, meaning that encryption (*described below*) and decryption occur client-side. When you create a Send:
+Sends are a secure and ephemeral mechanism for transmitting sensitive information to anyone, include plaintext and files. As the [About Send]({{site.baseurl}}/about-send/) article notes, Sends are **end-to-end encrypted**, meaning that encryption (*described below*) and decryption occur client-side. When you create a Send:
 
 1. A new 128-bit secret key is generated for the Send.
 2. Using HKDF-SHA256, a 512-bit encryption key is derived from the secret key.
@@ -21,7 +21,7 @@ Sends are a secure and ephemeral mechanism for transmitting sensitive informatio
 
 ## Send Decryption
 
-Sends are decrypted by opening the [Send link]({% link _articles/send/receive-send.md %}), which are constructed from a unique Send ID and the derived encryption key:
+Sends are decrypted by opening the [Send link]({{site.baseurl}}/receive-send/), which are constructed from a unique Send ID and the derived encryption key:
 
 `https://vault.bitwarden.com/#/send/send_id/encryption_key`
 

_articles/send/send-hosting.md

@@ -8,7 +8,7 @@ tags: []
 order: "08"
 ---
 
-Once you [update your instance]({% link _articles/hosting/updating-on-premise.md %}), most implementations will be already setup to begin [using Send]({% link _articles/send/create-send.md %}). An exception to this is if you're using a non-default **mapped volume for attachment storage**.
+Once you [update your instance]({{site.baseurl}}/updating-on-premise/), most implementations will be already setup to begin [using Send]({{site.baseurl}}/create-send/). An exception to this is if you're using a non-default **mapped volume for attachment storage**.
 
 The files attached to File Sends are stored in a `send` subdirectory of the existing attachments volume (i.e. `./bwdata/core/attachments/send`). This is dictated by the `globalSettings__send__baseDirectory=` environment variable, which has the following default configuration in `global.override.env`:
 

_articles/send/send-lifespan.md

@@ -193,7 +193,7 @@ To disable a Send from the CLI, you'll need to use the `edit` command to change
 bw send get <id> | jq '.disabled=false' | bw encode | bw send edit
 ```
 
-We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article for complete information on using Send from the CLI.
+We recommend reading the [Send from CLI]({{site.baseurl}}/send-cli/) article for complete information on using Send from the CLI.
 
 #### Delete from the CLI
 
@@ -203,7 +203,7 @@ To delete a Send from the CLI, use the `delete` command with the Send's exact un
 bw send delete <id>
 ```
 
-We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article for complete information on using Send from the CLI.
+We recommend reading the [Send from CLI]({{site.baseurl}}/send-cli/) article for complete information on using Send from the CLI.
 
 {% endcapture %}
 {{ cli_info | markdownify}}