Promote to Master (#748)

* initial commit

* adding quotes for the array error

* Create Gemfile

* Create Gemfile.lock

* add .nvmrc and .node-version

* removed /article from URL

* update links to work with netlify

* more fixed links

* link fixes

* update bad links

* Update netlify.toml

toml test for redirects

* article redirect

* link fixes

* Update index.html

* Update netlify.toml

* Update _config.yml

* Update netlify.toml

* Update netlify.toml

* Update netlify.toml

* Update netlify.toml

* Update netlify.toml

* add article back into URL for launch

* Update netlify.toml

* Update netlify.toml

* add order to categories front matter

* Update netlify.toml

* update

* sidemenu update

* Revert "sidemenu update"

This reverts commit 5441c3d35c.

* update order prop

* Navbar updates per Gary and compiler warnings

* font/style tweaks

* Update sidebar.html

* Stage Release Documentation (#739)

* initial drafts

* rewrite Custom Fields article to prioritize new context-menu option & better organize ancillary information

* edit

* edit

* Custom Field Context Menu & CAPTCHA item in release notes

* SSO relink event

* update rn

* small edits

* improve release notes titles

* fix side menu

* Edits courtest of mportune!

* update order

* link fixes

* link cleanup

* image updates and a link

* fix trailing slash

Co-authored-by: DanHillesheim <79476558+DanHillesheim@users.noreply.github.com>

_articles/providers/add-existing-client-org.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 05
+order: "05"
 ---
 
 MSPs, Resellers, and other Bitwarden Partners that are already administering Organizations on behalf of their clients can add pre-existing Organizations to their Provider Portal.

_articles/providers/client-org-setup.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 04
+order: "04"
 ---
 
 This article will walk you through the [creation of a Client Organization](#create-a-client-organization) and outline a typical [setup procedure](#initial-setup-procedure) for getting started administering a customer's Organization.
@@ -24,7 +24,7 @@ To create a Client Organization you must be a [Provider Admin]({{site.baseurl}}/
    {% image providers/provider-add-client.png Create a Client Organization %}
 2. On the New Client Organization screen, enter an **Organization Name**, **Billing Email**, and **Client Owner Email**.
 
-   {% callout info %}An invitation will automatically be sent to the **Client Owner Email** to join the Organization as an [Owner]({{site.baseurl}}/article/user-types-access-control).{% endcallout %}
+   {% callout info %}An invitation will automatically be sent to the **Client Owner Email** to join the Organization as an [Owner]({{site.baseurl}}/article/user-types-access-control/).{% endcallout %}
 3. From the **Choose Your Plan** list, select the [type of Organization]({{site.baseurl}}/article/about-bitwarden-plans/#compare-the-plans-1) to create.
 
    {% callout success %}Teams and Enterprise Organizations include premium features for all enrolled users.{% endcallout %}

_articles/providers/getting-started-providers.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 02
+order: "02"
 redirect_from:
   - /article/deploying-bitwarden-as-a-msp/
 ---
@@ -43,7 +43,7 @@ Selecting the **Setup Provider Now** button will prompt you to log in to Bitward
 
 ### Onboard Users
 
-As the creator of the Provider, you'll be automatically given [Provider Admin]({{site.baseurl}}/provider-users/#provider-user-types) status, allowing you to fully manage all aspects of the Provider and all [Client Organizations](#client-organizations). Bitwarden strongly recommends that you provision a second Provider Admin for failover purposes.
+As the creator of the Provider, you'll be automatically given [Provider Admin]({{site.baseurl}}/article/provider-users/#provider-user-types) status, allowing you to fully manage all aspects of the Provider and all [Client Organizations](#client-organizations). Bitwarden strongly recommends that you provision a second Provider Admin for failover purposes.
 
 Now, begin adding your employees as [Service Users]({{site.baseurl}}/article/provider-users/#provider-user-types), which will allow them to fully administer all Client Organizations and create new ones or manage the Provider itself:
 
@@ -107,6 +107,6 @@ With the infrastructure for securely and scalably sharing credentials in place,
 
    {% image organizations/org-people-invite.png %}
 
-2. **For larger customers** who leverage a directory service (Active Directory, LDAP, Okta, etc.), use [Directory Connector]({{site.baseurl}}/article/directory-sync) to sync Organization users from the source directory and automatically issue invitations.
+2. **For larger customers** who leverage a directory service (Active Directory, LDAP, Okta, etc.), use [Directory Connector]({{site.baseurl}}/article/directory-sync/) to sync Organization users from the source directory and automatically issue invitations.
 
 Regardless of whether you've invited users from the Organization Vault or using Directory Connector, the same 3-step process (Invite → Accept → Confirm) that you followed when [onboarding Provider users](#onboard-users) will apply here as well.

_articles/providers/manage-client-orgs.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 06
+order: "06"
 ---
 
 To access a [Client Organization]({{site.baseurl}}/article/providers/#client-organizations) as a [Service User]({{site.baseurl}}/article/provider-users/#provider-user-types), select **Provider** from the top navigation and select your Provider from the Providers list. In the Provider Portal, select the Client Organization to administer from the {% icon fa-bank %} **Clients** tab:
@@ -20,10 +20,10 @@ Once in the Organization Vault you can fully administer the Client Organization,
 |Add and Remove Users|Onboard and offboard users from Bitwarden as they join and leave the customers' Organization.|[User Onboarding]({{site.baseurl}}/article/managing-users/#onboard)<br><br>[User Offboarding]({{site.baseurl}}/article/managing-users/#offboard)|
 |Change User Permissions|When end-users change roles, change their permissions as appropriate.|[User Types and Access Control]({{site.baseurl}}/article/user-types-access-control/)|
 |Add and Remove User Seats|As the customers' business grows, manage the number of user seats for the Client Organization.|[Manage User Seats]({{site.baseurl}}/article/managing-users/#manage-user-seats)|
-|Reset Users' Master Passwords|If enabled, use Admin Password Reset to recover end-user accounts if they forget their Master Password.|[Admin Password Reset]({{site.baseurl}}/article/admin-reset)|
+|Reset Users' Master Passwords|If enabled, use Admin Password Reset to recover end-user accounts if they forget their Master Password.|[Admin Password Reset]({{site.baseurl}}/article/admin-reset/)|
 |Create & Share Vault Items|Add and share new Vault items on-the-fly when users need access to new systems.|[Sharing]({{site.baseurl}}/article/sharing/)|
-|Secure one-time Sharing|Use Bitwarden for secure one-time sharing of credentials, documents, and more.|[Create a Send]({{site.baseurl}}/article/create-send)|
-|Monitor Vault Health|Use Organization Vault Health Reports and Event Logs to keep an eye on the overall health of the Client Organization.|[Vault Health Reports]({{site.baseurl}}/article/reports/)<br><br>[Event Logs]({{site.baseurl}}/article/events/)|
+|Secure one-time Sharing|Use Bitwarden for secure one-time sharing of credentials, documents, and more.|[Create a Send]({{site.baseurl}}/article/create-send/)|
+|Monitor Vault Health|Use Organization Vault Health Reports and Event Logs to keep an eye on the overall health of the Client Organization.|[Vault Health Reports]({{site.baseurl}}/article/reports/)<br><br>[Event Logs]({{site.baseurl}}/article/event-logs/)|
 |Manage Billing|Make changes to the billing information for the Client Organization, if you ever need to.|[Update Billing Info]({{site.baseurl}}/article/update-billing-info/#update-billing-information-for-organizations)|
 
 Additionally, **if your Service Users help to train customers' end-users to use Bitwarden**, the following resources may be helpful:

_articles/providers/provider-events.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 07
+order: "07"
 ---
 
 ## What are Event Logs?

_articles/providers/provider-users.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 03
+order: "03"
 ---
 
 ## Onboard Provider Users
@@ -49,7 +49,7 @@ To confirm accepted invitations to your Provider:
 3. Select any `Accepted` users and use the {% icon fa-cog %} gear dropdown to {% icon fa-check %} **Confirm Selected**:
 
    {% image /providers/provider-confirm.png Confirm Provider Users %}
-4. On the panel that appears, verify that the [fingerprint phrases]({{site.baseurl}}/article/fingerprint-phrase) for new users match those they can find in their **Settings** → **My Account** screen.
+4. On the panel that appears, verify that the [fingerprint phrases]({{site.baseurl}}/article/fingerprint-phrase/) for new users match those they can find in their **Settings** → **My Account** screen.
 
    Each fingerprint phrase is unique to its account, and ensures a final layer of oversight in securely adding users. If they match, select **Confirm**.
 

_articles/providers/providers.md

@@ -6,7 +6,7 @@ featured: false
 popular: false
 hidden: false
 tags: []
-order: 01
+order: "01"
 ---
 
 {% callout success %}
@@ -31,7 +31,7 @@ The Provider Portal is an all-in-one management experience that enables Provider
 
 {% image providers/provider.png Provider Portal %}
 
-Providers are built with two distinct [user types]({{site.baseurl}}/artice/provider-users/#user-types):
+Providers are built with two distinct [user types]({{site.baseurl}}/article/provider-users/#provider-user-types):
 
 - **Service Users** can fully administer [Client Organizations](#client-organizations).
 - **Provider Admins** can administer [Client Organizations](#client-organizations) and administer the Provider itself, including adding new Service Users to the team.
@@ -43,9 +43,9 @@ Client Organizations are any [Organization]({{site.baseurl}}/article/about-organ
 {% image providers/provider-diagram.png Structure of a Provider %}
 
 {% callout info %}
-**As denoted in the above diagram**, if Providers want to use an [Organization]({{site.baseurl}}/article/about-organizations) to manage their own credentials, they **should not** include it as a Client Organization that's administered by the Provider.
+**As denoted in the above diagram**, if Providers want to use an [Organization]({{site.baseurl}}/article/about-organizations/) to manage their own credentials, they **should not** include it as a Client Organization that's administered by the Provider.
 
-Creating an independent Organization for this case will ensure users can be given the appropriate [user types and access controls]({{site.baseurl}}/article/user-types-access-control) over credentials.
+Creating an independent Organization for this case will ensure users can be given the appropriate [user types and access controls]({{site.baseurl}}/article/user-types-access-control/) over credentials.
 {% endcallout %}
 
 Organizations relate Bitwarden users and Vault items together for [secure sharing]({{site.baseurl}}/article/sharing/) of Logins, Cards, Notes, and Identities. Organizations have a unique Vault, where Provider Service Users can manage the Organization's items, users, and settings:
@@ -56,4 +56,4 @@ Members of a Client Organization (i.e. your customer's end-users) will find shar
 
 {% image organizations/personal-vault-org-enabled.png End-user Vault %}
 
-Once you've filled out the [Provider Registration form](#) and been setup with a Provider by a member of the Bitwarden team, [start a Client Organization]({{site.baseurl}}/article/client-org-setup).
+Once you've [contacted us](https://bitwarden.com/contact) and been setup with a Provider by a member of the Bitwarden team, [start a Client Organization]({{site.baseurl}}/article/client-org-setup/).