diff --git a/.prettierrc b/.prettierrc
index f8d45edb52..8d0df3d705 100644
--- a/.prettierrc
+++ b/.prettierrc
@@ -1,5 +1,6 @@
 {
 	"printWidth": 100,
 	"singleQuote": true,
-	"useTabs": true
+	"useTabs": true,
+	"proseWrap": "always"
 }
diff --git a/docs/concepts/activity-and-versions.md b/docs/concepts/activity-and-versions.md
index 15c8fb1084..fc6741df7a 100644
--- a/docs/concepts/activity-and-versions.md
+++ b/docs/concepts/activity-and-versions.md
@@ -1,10 +1,15 @@
 # Activity & Versions
 
-> Directus stores detailed records of all changes made to data through the App and API. This gives a comprehensive accountability log of who did what, and when. This also powers the Directus versioning system, which allows storing alternate versions/revisions of items.
+> Directus stores detailed records of all changes made to data through the App and API. This gives a
+> comprehensive accountability log of who did what, and when. This also powers the Directus
+> versioning system, which allows storing alternate versions/revisions of items.
 
 ## Activity
 
-This is a log of all events that have occured within the project. Activity can be accessed in two ways, via the main [Activity Module](/concepts/app-overview#actvity-history), or within the sidebar of individual [Item Detail](/concepts/app-overview#item-detail) pages. The following information is stored for each event's activity item:
+This is a log of all events that have occured within the project. Activity can be accessed in two
+ways, via the main [Activity Module](/concepts/app-overview#actvity-history), or within the sidebar
+of individual [Item Detail](/concepts/app-overview#item-detail) pages. The following information is
+stored for each event's activity item:
 
 -   Action
 -   User
@@ -15,28 +20,31 @@ This is a log of all events that have occured within the project. Activity can b
 -   Item
 -   Comment (when applicable)
 
-::: tip Readonly
-For proper accountability, activity records are readonly. Administrators should avoid changing, deleting, or truncating this data.
-:::
+::: tip Readonly For proper accountability, activity records are readonly. Administrators should
+avoid changing, deleting, or truncating this data. :::
 
-::: warning External Events
-Directus can only track events that pass through the platform's middleware. Changes made directly to the database, or by other external means, are not included in the activity log.
-:::
+::: warning External Events Directus can only track events that pass through the platform's
+middleware. Changes made directly to the database, or by other external means, are not included in
+the activity log. :::
 
 ## Versions
 
-Every change made to items in Directus are also stored as a versioned snapshot. This additional data is also linked to the specific Activity event which created it. Below are the two key pieces of information stored for each version:
+Every change made to items in Directus are also stored as a versioned snapshot. This additional data
+is also linked to the specific Activity event which created it. Below are the two key pieces of
+information stored for each version:
 
 -   Data — A full snapshot of the item _after_ the event
 -   Delta — The specific field data changed by this event
 
-::: tip Customizing Version Data
-Since versions store a full data snapshot and delta, the `directus_revisions` collection can quickly grow quite large, increasing database size and potentially decreasing performance. To remedy this, Directus allows [configuring version scope](/concepts/app-overview) per collection to set the exact field data saved.
-:::
+::: tip Customizing Version Data Since versions store a full data snapshot and delta, the
+`directus_revisions` collection can quickly grow quite large, increasing database size and
+potentially decreasing performance. To remedy this, Directus allows
+[configuring version scope](/concepts/app-overview) per collection to set the exact field data
+saved. :::
 
-::: tip Creating Detached Versions
-You can also create a new version for an item without saving the data to the parent item itself. This allows you to "stage" changes to an item that may already be live/published.
-:::
+::: tip Creating Detached Versions You can also create a new version for an item without saving the
+data to the parent item itself. This allows you to "stage" changes to an item that may already be
+live/published. :::
 
 ### Relevant Guides
 
diff --git a/docs/concepts/app-extensions.md b/docs/concepts/app-extensions.md
index 9f98edca26..407508acbe 100644
--- a/docs/concepts/app-extensions.md
+++ b/docs/concepts/app-extensions.md
@@ -1,10 +1,14 @@
 # App Components
 
-> Directus has been architected as completely modular and extensible. There are four keystone component types within the App. Out-of-the-box components are configurable, or altogether new components can be created as extensions.
+> Directus has been architected as completely modular and extensible. There are four keystone
+> component types within the App. Out-of-the-box components are configurable, or altogether new
+> components can be created as extensions.
 
 ## Modules
 
-Modules are the highest and broadest level of organization within the App. All core functionality within the App (other than authentication and activity) can be bucketed into one of the following five modules:
+Modules are the highest and broadest level of organization within the App. All core functionality
+within the App (other than authentication and activity) can be bucketed into one of the following
+five modules:
 
 -   Collections — The primary way to view and interact with database content
 -   User Directory — A dedicated section for the platform's system Users
@@ -12,7 +16,9 @@ Modules are the highest and broadest level of organization within the App. All c
 -   Documentation — A tailored, in-app portal for the platform's concepts, guides, and reference
 -   Settings — An Admin-Only section for configuring the project and system settings
 
-In addition to these core modules, custom modules offer a _blank canvas_ for creating altogether new/different experiences within the App, such as proprietary dashboards, compound datasets, or third-party integrations (eg: a Stripe Payments Console).
+In addition to these core modules, custom modules offer a _blank canvas_ for creating altogether
+new/different experiences within the App, such as proprietary dashboards, compound datasets, or
+third-party integrations (eg: a Stripe Payments Console).
 
 ### Relevant Guides
 
@@ -20,11 +26,15 @@ In addition to these core modules, custom modules offer a _blank canvas_ for cre
 
 ## Layouts
 
-Layouts provide different ways for presenting, browsing, visualizing, or even managing sets of data. Most commonly shown on Collection Detail pages and contextual modals for item selection. Directus includes several Layout options out-of-the-box, each with different features and configuration options.
+Layouts provide different ways for presenting, browsing, visualizing, or even managing sets of data.
+Most commonly shown on Collection Detail pages and contextual modals for item selection. Directus
+includes several Layout options out-of-the-box, each with different features and configuration
+options.
 
 ### Table
 
-This tabular layout supports all forms of data, and is therefore the default within the Collections module. It includes the following features/options:
+This tabular layout supports all forms of data, and is therefore the default within the Collections
+module. It includes the following features/options:
 
 -   Toggle & Reorder Field Columns (Option)
 -   Row Spacing (Option)
@@ -35,7 +45,9 @@ This tabular layout supports all forms of data, and is therefore the default wit
 
 ### Cards
 
-This tiled layout is ideal for collections that prioritize an image. It is the default for both the [User Directory](/guides/users) (shows the avatar) and [File Library](/guides/files) (shows asset thumbnail). It includes the following features/options:
+This tiled layout is ideal for collections that prioritize an image. It is the default for both the
+[User Directory](/guides/users) (shows the avatar) and [File Library](/guides/files) (shows asset
+thumbnail). It includes the following features/options:
 
 -   Image Source (Option)
 -   Title (Option)
@@ -60,12 +72,19 @@ In addition to these core layouts, custom layouts allow for creating more tailor
 
 ## Interfaces
 
-Interfaces provide a multitude of ways to view or interact with field data on [Item Detail](/concepts/app-overview#item-detail) page forms. Every interface supports a specific subset of field [types](/reference/field-types) (eg: String), which determines how the data will be stored. For example, the _Text Input_ interface can manage most types of data, but might not be ideal for dates, where a _Calendar_ interface excels. Directus includes many Interfaces out-of-the-box:
+Interfaces provide a multitude of ways to view or interact with field data on
+[Item Detail](/concepts/app-overview#item-detail) page forms. Every interface supports a specific
+subset of field [types](/reference/field-types) (eg: String), which determines how the data will be
+stored. For example, the _Text Input_ interface can manage most types of data, but might not be
+ideal for dates, where a _Calendar_ interface excels. Directus includes many Interfaces
+out-of-the-box:
 
 -   Text Input
 -   @TODO List all core interfaces, or link to a exhaustive reference?
 
-In addition to these core interfaces, custom interfaces allow for creating more tailored or proprietary ways to view or manage field data, such as bespoke layout builders, skeuomorphic knobs, or relational views for third-party data (eg: Stripe Credit Card UI).
+In addition to these core interfaces, custom interfaces allow for creating more tailored or
+proprietary ways to view or manage field data, such as bespoke layout builders, skeuomorphic knobs,
+or relational views for third-party data (eg: Stripe Credit Card UI).
 
 ### Relevant Guides
 
@@ -73,13 +92,19 @@ In addition to these core interfaces, custom interfaces allow for creating more
 
 ## Displays
 
-Displays are the smaller, read-only counterpart to Interfaces, defining how a field's data will be displayed inline on [Item Detail](/concepts/app-overview#item-detail) pages, Modals, and even within Interfaces themselves. For example, you may have a "Status" field that uses a _Dropdown_ Interface on the Item Detail page, and a _Color Dot_ Display when the field is referenced throughout the rest of the App. Directus includes many Displays out-of-the-box:
+Displays are the smaller, read-only counterpart to Interfaces, defining how a field's data will be
+displayed inline on [Item Detail](/concepts/app-overview#item-detail) pages, Modals, and even within
+Interfaces themselves. For example, you may have a "Status" field that uses a _Dropdown_ Interface
+on the Item Detail page, and a _Color Dot_ Display when the field is referenced throughout the rest
+of the App. Directus includes many Displays out-of-the-box:
 
 -   Raw
 -   Formatted Value
 -   @TODO List all core interfaces, or link to a exhaustive reference?
 
-In addition to these core displays, custom displays allow for creating customized ways to view or represent field data, such as progress indicators, relational data tooltips, or specific formatting options.
+In addition to these core displays, custom displays allow for creating customized ways to view or
+represent field data, such as progress indicators, relational data tooltips, or specific formatting
+options.
 
 ### Relevant Guides
 
@@ -87,7 +112,12 @@ In addition to these core displays, custom displays allow for creating customize
 
 ## Title Formatter
 
-Directus uses [Database Mirroring](/concepts/platform-overview) to create its underlying data model based on your custom schema. Therefore the App needs a reliable way of converting any raw table name, field name, or other technical value into a prettified format that is human-readable. At its core, the Title Formatter converts any string into title-case with proper whitespace. It also covers acronyms, initialisms, common proper nouns, so each is output properly. Some example conversion include:
+Directus uses [Database Mirroring](/concepts/platform-overview) to create its underlying data model
+based on your custom schema. Therefore the App needs a reliable way of converting any raw table
+name, field name, or other technical value into a prettified format that is human-readable. At its
+core, the Title Formatter converts any string into title-case with proper whitespace. It also covers
+acronyms, initialisms, common proper nouns, so each is output properly. Some example conversion
+include:
 
 | Original String              | Formatted Title                   |
 | ---------------------------- | --------------------------------- |
diff --git a/docs/concepts/app-overview.md b/docs/concepts/app-overview.md
index 76cb859ec3..a96419109c 100644
--- a/docs/concepts/app-overview.md
+++ b/docs/concepts/app-overview.md
@@ -1,6 +1,8 @@
 # App Overview
 
-> The Directus App is the presentation layer for your data, content, and assets. It uses a left-to-right visual hierarchy for organization and navigation. Below we cover the App's global elements and individual pages.
+> The Directus App is the presentation layer for your data, content, and assets. It uses a
+> left-to-right visual hierarchy for organization and navigation. Below we cover the App's global
+> elements and individual pages.
 
 ## Global Elements
 
@@ -9,20 +11,29 @@
 
 ### 1. Module Bar
 
--   **Project Logo** — Displays your configured project logo and project color (defaults to the Directus logo and color). If configured, clicking this component will navigate to the Project URL. During platform activity, an indeterminate progress indicator will also be shown here.
--   **Modules** — Any available modules are listed below the project logo. These may be turned off or reordered based on your [role's configuration](/concepts/users-roles-and-permissions), but by default this includes:
+-   **Project Logo** — Displays your configured project logo and project color (defaults to the
+    Directus logo and color). If configured, clicking this component will navigate to the Project
+    URL. During platform activity, an indeterminate progress indicator will also be shown here.
+-   **Modules** — Any available modules are listed below the project logo. These may be turned off
+    or reordered based on your [role's configuration](/concepts/users-roles-and-permissions), but by
+    default this includes:
     -   [Collections](/concepts/app-overview)
     -   [User Directory](/concepts/app-overview)
     -   [File Library](/concepts/app-overview)
     -   [Documentation](/concepts/app-overview)
     -   [Settings](/concepts/app-overview) — Admin only
     -   [Custom Modules](/guides/extensions/modules) — If configured
--   **Current User Menu** — This component displays the authenticated user's name and avatar. Hovering over this menu exposes the Log Out button.
+-   **Current User Menu** — This component displays the authenticated user's name and avatar.
+    Hovering over this menu exposes the Log Out button.
 
 ### 2. Navigation Bar
 
--   **Project Name** — Shows the name of your current project (see [Project Settings](/guides/white-labeling)), as well as the quality of your project's API connection.
--   **Navigation** — This is a dynamic navigation based on your current module. Some modules also support [Presets and/or Bookmarks](/guides/roles-and-permissions), which are ways to link to more specific data-sets.
+-   **Project Name** — Shows the name of your current project (see
+    [Project Settings](/guides/white-labeling)), as well as the quality of your project's API
+    connection.
+-   **Navigation** — This is a dynamic navigation based on your current module. Some modules also
+    support [Presets and/or Bookmarks](/guides/roles-and-permissions), which are ways to link to
+    more specific data-sets.
 
 ### 3. Page
 
@@ -30,25 +41,35 @@
     -   Page Icon — Clicking this navigates back to the previous page
     -   Module Title — Clicking this navigates to the parent module/section
     -   Page Title — Displays the current page's title
-    -   Action Buttons — On the right-side of the header are contextual buttons for specific page actions. Please note that some primary action buttons have a "..." icon beside them that provides additional options when clicked.
+    -   Action Buttons — On the right-side of the header are contextual buttons for specific page
+        actions. Please note that some primary action buttons have a "..." icon beside them that
+        provides additional options when clicked.
 -   **Page Content** — This displays the content of the page you navigated to.
 
 ### 4. Page Sidebar
 
--   **Page Components** — Lists any contextual page components available. The "Info" component is available on every page, explaining the page's general purpose and relevant details. Clicking any sidebar component will accordion it open. If the App window is large enough, the sidebar will automatically open, and can be closed by clicking the "X" in the top-right.
--   **Notifications Tray** — Fixed to the bottom of the page sidebar, this button opens a tray of recent user notifications, and provides a link to the [Activity History](/concepts/app-overview) page.
+-   **Page Components** — Lists any contextual page components available. The "Info" component is
+    available on every page, explaining the page's general purpose and relevant details. Clicking
+    any sidebar component will accordion it open. If the App window is large enough, the sidebar
+    will automatically open, and can be closed by clicking the "X" in the top-right.
+-   **Notifications Tray** — Fixed to the bottom of the page sidebar, this button opens a tray of
+    recent user notifications, and provides a link to the [Activity History](/concepts/app-overview)
+    page.
 
 ## Collections
 
-This module is the primary way for interacting with your database content. Here you can access your collections, browse their items, and navigate to individual item forms.
+This module is the primary way for interacting with your database content. Here you can access your
+collections, browse their items, and navigate to individual item forms.
 
 ### Collection Listing
 
-A page that lists the collections available to the current user. This is the landing page of the module, and effectively the same as its navigation listing.
+A page that lists the collections available to the current user. This is the landing page of the
+module, and effectively the same as its navigation listing.
 
 ### Collection Detail
 
-Provides a configurable layout to browse or visualize items within a given collection. Like other browse pages, there are many available features, including:
+Provides a configurable layout to browse or visualize items within a given collection. Like other
+browse pages, there are many available features, including:
 
 -   [Creating Items](/guides/items#creating-items)
 -   [Browsing Items](/guides/items#browsing-items)
@@ -62,7 +83,9 @@ Provides a configurable layout to browse or visualize items within a given colle
 
 ### Item Detail
 
-Most layouts on the browse page support navigating to individual item detail pages, where you a presented with a [customizable form](/guides/fields#adjusting-fields-layout) for viewing/editing the item's content. Like other detail pages, there are many available features, including:
+Most layouts on the browse page support navigating to individual item detail pages, where you a
+presented with a [customizable form](/guides/fields#adjusting-fields-layout) for viewing/editing the
+item's content. Like other detail pages, there are many available features, including:
 
 -   [Updating an Item](/guides/items#updating-item)
 -   [Reverting an Item](/guides/items#reverting-item)
@@ -71,11 +94,15 @@ Most layouts on the browse page support navigating to individual item detail pag
 
 ## User Directory
 
-A module includes a comprehensive listing of all system users within your project. This page has the same features and configuration as [Collection Detail](/concepts/app-overview).
+A module includes a comprehensive listing of all system users within your project. This page has the
+same features and configuration as [Collection Detail](/concepts/app-overview).
 
 ### User Detail
 
-Similar to other [Item Detail](/concepts/app-overview) pages, this page provides a custom form for viewing system users. This is also used for editing the "Profile Page" of the current user, which is accessible from the [User Menu](/concepts/app-overview). Directus ships with a full-featured user system, with the following fields:
+Similar to other [Item Detail](/concepts/app-overview) pages, this page provides a custom form for
+viewing system users. This is also used for editing the "Profile Page" of the current user, which is
+accessible from the [User Menu](/concepts/app-overview). Directus ships with a full-featured user
+system, with the following fields:
 
 -   **First Name** — The user's given name
 -   **Last Name** — The user's family name
@@ -100,20 +127,23 @@ The sidebar's info component also includes the following readonly details:
 -   **Last Access** — The timestamp of the user's last App or API action
 -   **Last Page** — The last App page accessed by the user
 
-::: tip Extending Users
-While the fields included out-of-the-box are locked from schema changes, you can extend Directus Users to include
-additional proprietary fields within [Settings > Data Model](/concepts/data-model).
-:::
+::: tip Extending Users While the fields included out-of-the-box are locked from schema changes, you
+can extend Directus Users to include additional proprietary fields within
+[Settings > Data Model](/concepts/data-model). :::
 
 ## File Library
 
-This module aggregates all files within the project into one consolidated library. This page has the same features and configuration as [Collection Detail](/concepts/app-overview).
+This module aggregates all files within the project into one consolidated library. This page has the
+same features and configuration as [Collection Detail](/concepts/app-overview).
 
 ### File Detail
 
-Similar to other [Item Detail](/concepts/app-overview) pages, this page provides a custom form for viewing assets and embeds. Directus ships with a full-featured system for digital asset management, with the following fields:
+Similar to other [Item Detail](/concepts/app-overview) pages, this page provides a custom form for
+viewing assets and embeds. Directus ships with a full-featured system for digital asset management,
+with the following fields:
 
--   **Title** — Pulled from the file metadata if available, falls back to a formatted version of the filename
+-   **Title** — Pulled from the file metadata if available, falls back to a formatted version of the
+    filename
 -   **Description** — Pulled from the file metadata if available
 -   **Tags** — Pulled from the file metadata if available
 -   **Location** — Pulled from the file metadata if available
@@ -131,30 +161,39 @@ The sidebar's info component also includes the following readonly details:
 -   **Folder** — The current parent folder that contains the file
 -   **Metadata** — Metadata JSON dump of the file's EXIF, IPTC, and ICC information
 
-::: tip Extending Files
-While the fields included out-of-the-box are locked from schema changes, you can extend Directus Files to include additional proprietary fields within [Settings > Data Model](/concepts/data-model).
-:::
+::: tip Extending Files While the fields included out-of-the-box are locked from schema changes, you
+can extend Directus Files to include additional proprietary fields within
+[Settings > Data Model](/concepts/data-model). :::
 
 ## Documentation
 
-This module is an internal set of guides, concepts, and reference docs for your project's specific version of Directus. It also includes a dynamic [API Reference](/reference/api/introduction) that is dynamically tailored to your custom schema. The docs are organized into four distinct sections:
+This module is an internal set of guides, concepts, and reference docs for your project's specific
+version of Directus. It also includes a dynamic [API Reference](/reference/api/introduction) that is
+dynamically tailored to your custom schema. The docs are organized into four distinct sections:
 
--   [Getting Started](/getting-started/introduction)\*\* — Novice Oriented. For a platform intro and installation.
+-   [Getting Started](/getting-started/introduction)\*\* — Novice Oriented. For a platform intro and
+    installation.
 -   [Concepts](/concepts/app-overview)\*\* — Learning Oriented. For understanding the platform.
--   [Guides](/concepts/roles-and-permissions)\*\* — Problem Oriented. Follow along with steps while working.
--   [Reference](/reference/api/introduction)\*\* — Information Oriented. Look up info and specs while working.
+-   [Guides](/concepts/roles-and-permissions)\*\* — Problem Oriented. Follow along with steps while
+    working.
+-   [Reference](/reference/api/introduction)\*\* — Information Oriented. Look up info and specs
+    while working.
 
-::: tip Updating the Docs
-Our docs are written in markdown (with some additional VuePress styling like this hint box), and available for editing/fixing via [GitHub](https://github.com/directus/directus).
-:::
+::: tip Updating the Docs Our docs are written in markdown (with some additional VuePress styling
+like this hint box), and available for editing/fixing via
+[GitHub](https://github.com/directus/directus). :::
 
 ## Activity History
 
-This module provides a collective timeline of all actions taken within the project. This is a great way to audit user activity or enforce accountability. This is the only system module that is not in the module bar by default — instead being located within the notifications tray of the page sidebar. This page has the same features and configuration as [Collection Detail](/concepts/app-overview).
+This module provides a collective timeline of all actions taken within the project. This is a great
+way to audit user activity or enforce accountability. This is the only system module that is not in
+the module bar by default — instead being located within the notifications tray of the page sidebar.
+This page has the same features and configuration as [Collection Detail](/concepts/app-overview).
 
 ### Activity Detail
 
-Unlike other item detail pages, activity items are **readonly** (for proper accountability) and open in a modal window with the following fields:
+Unlike other item detail pages, activity items are **readonly** (for proper accountability) and open
+in a modal window with the following fields:
 
 -   **User** — The Directus user that performed the action
 -   **Action** — The specific action taken, eg: Create, Update, Delete, Authenticate, etc
@@ -166,7 +205,9 @@ Unlike other item detail pages, activity items are **readonly** (for proper acco
 
 # Settings
 
-This module is only available to users within [admin roles](/concepts/users-roles-and-permissions#administrators-role). This is where your project is configured, and the first place to go after installation. It includes the following sections:
+This module is only available to users within
+[admin roles](/concepts/users-roles-and-permissions#administrators-role). This is where your project
+is configured, and the first place to go after installation. It includes the following sections:
 
 -   [Project Settings](/concepts/platform-overview)
 -   [Data Model](/concepts/data-model)
diff --git a/docs/concepts/files-and-thumbnails.md b/docs/concepts/files-and-thumbnails.md
index c6e96afb66..f81dbd0333 100644
--- a/docs/concepts/files-and-thumbnails.md
+++ b/docs/concepts/files-and-thumbnails.md
@@ -1,10 +1,13 @@
 # Files & Thumbnails
 
-> Directus offers a full Digital Asset Management (DAM) system. This includes multiple storage adapters, nested folder organization, private file access, image editing, and on-demand thumbnail generation.
+> Directus offers a full Digital Asset Management (DAM) system. This includes multiple storage
+> adapters, nested folder organization, private file access, image editing, and on-demand thumbnail
+> generation.
 
 ## Storage Adapters
 
-Storage adapters allow project files to be stored in different locations or services. By default, Directus includes the following adapters:
+Storage adapters allow project files to be stored in different locations or services. By default,
+Directus includes the following adapters:
 
 -   **Local Filesystem** — The default, any filesystem location or network-attached storage
 -   **S3 or Equivalent** — Including AWS S3, DigitalOcean Spaces, Alibaba OSS, and others
@@ -12,7 +15,10 @@ Storage adapters allow project files to be stored in different locations or serv
 
 ## Files
 
-Directus allows you to manage all your files in one place, including documents, images, videos, and more. Files can be uploaded to the [File Library](/concepts/app-overview#file-library) in general, or directly to an item via a [Single File](/guides/field-types/single-file) or [Multiple Files](/guides/field-types/multiple-files) field.
+Directus allows you to manage all your files in one place, including documents, images, videos, and
+more. Files can be uploaded to the [File Library](/concepts/app-overview#file-library) in general,
+or directly to an item via a [Single File](/guides/field-types/single-file) or
+[Multiple Files](/guides/field-types/multiple-files) field.
 
 ### Relevant Guides
 
@@ -21,13 +27,20 @@ Directus allows you to manage all your files in one place, including documents,
 
 ## Embedded Assets
 
-Directus also supports ingesting third-party embedded assets, such as YouTube or Vimeo videos. These are managed the same as normal files, however the resource itself is stored on the external service, and referenced via its proprietary UID.
+Directus also supports ingesting third-party embedded assets, such as YouTube or Vimeo videos. These
+are managed the same as normal files, however the resource itself is stored on the external service,
+and referenced via its proprietary UID.
 
 ## Crop & Transform Images
 
-Our file middleware also allows for cropping and transforming image assets on the fly. This means you can simply request an image, include any desired transformation parameters, and you'll be served the new asset as a response. This is very useful for automatically generating many different thumbnails/versions of an original file.
+Our file middleware also allows for cropping and transforming image assets on the fly. This means
+you can simply request an image, include any desired transformation parameters, and you'll be served
+the new asset as a response. This is very useful for automatically generating many different
+thumbnails/versions of an original file.
 
-To impede malicious users from consuming your storage by requesting a multitude of random sizes, Directus includes a [Asset Allow-List](/guides/files#creating-thumbnail-presets) to limit what transformations are possible.
+To impede malicious users from consuming your storage by requesting a multitude of random sizes,
+Directus includes a [Asset Allow-List](/guides/files#creating-thumbnail-presets) to limit what
+transformations are possible.
 
 ### Relevant Guides
 
diff --git a/docs/concepts/internationalization.md b/docs/concepts/internationalization.md
index c60ea13c7d..6e09f0d68a 100644
--- a/docs/concepts/internationalization.md
+++ b/docs/concepts/internationalization.md
@@ -1,23 +1,32 @@
 # Internationalization
 
-> Directus is maintained by people all over the world. Not only does Directus allow you to author and manage multilingual content, the App itself also supports multiple languages and locales.
+> Directus is maintained by people all over the world. Not only does Directus allow you to author
+> and manage multilingual content, the App itself also supports multiple languages and locales.
 
 ## App Translations
 
-Directus supports internationalization across its entire Admin App. Many languages are currently supported, with more are being added all the time. Help the communtiy by adding or refining your language through our [CrowdIn](https://locales.directus.io/) integration.
+Directus supports internationalization across its entire Admin App. Many languages are currently
+supported, with more are being added all the time. Help the communtiy by adding or refining your
+language through our [CrowdIn](https://locales.directus.io/) integration.
 
 ## Schema Translations
 
-Directus uses [database mirroring](#) to dynamically pull in your schema's tables and columns, however this only covers one language. Therefore our platform supports schema translations for these names, allowing you to properly support different languages for your Collection and Field names.
+Directus uses [database mirroring](#) to dynamically pull in your schema's tables and columns,
+however this only covers one language. Therefore our platform supports schema translations for these
+names, allowing you to properly support different languages for your Collection and Field names.
 
-::: tip Overriding Technical Names
-If your project requires more _technical_ table/column names (eg: `cust` or `f_name`), you can also use schema translations to override those defaults (eg: `Customers` or `First Name`) in the primary language.
-:::
+::: tip Overriding Technical Names If your project requires more _technical_ table/column names (eg:
+`cust` or `f_name`), you can also use schema translations to override those defaults (eg:
+`Customers` or `First Name`) in the primary language. :::
 
 ## Content Translations
 
-One of the most important features in Directus is the ability to author and manage multilingual content. While you can accomplish this by creating _standard_ fields in the parent collection for each language, it is more extensible to use our relational translation fields to dynamically manage content in as many languages as is required. Mixing standard and translated fields also allows language-agnostic data (such as dates or toggles) to remain within the parent collection.
+One of the most important features in Directus is the ability to author and manage multilingual
+content. While you can accomplish this by creating _standard_ fields in the parent collection for
+each language, it is more extensible to use our relational translation fields to dynamically manage
+content in as many languages as is required. Mixing standard and translated fields also allows
+language-agnostic data (such as dates or toggles) to remain within the parent collection.
 
-::: tip Custom Interfaces
-For more advanced use-cases, such as connecting to a third-party translation service, you can read our extension guide on [creating a custom interface](/guides/extensions/interfaces).
-:::
+::: tip Custom Interfaces For more advanced use-cases, such as connecting to a third-party
+translation service, you can read our extension guide on
+[creating a custom interface](/guides/extensions/interfaces). :::
diff --git a/docs/concepts/platform-overview.md b/docs/concepts/platform-overview.md
index 730f8557e4..9f46293a94 100644
--- a/docs/concepts/platform-overview.md
+++ b/docs/concepts/platform-overview.md
@@ -1,10 +1,14 @@
 # Platform Overview
 
-> The Directus platform is primarily comprised of an API and App, working in concert to manage the content of your SQL database.
+> The Directus platform is primarily comprised of an API and App, working in concert to manage the
+> content of your SQL database.
 
 ## Database Mirroring
 
-Instead of using a predefined "one-size-fits-all" data model to store your content, Directus "mirrors" your actual SQL database in real-time. The principle is akin to a database client (eg: _phpMyAdmin_), but includes far mor advanced tools, and is safe and intuitive enough for non-technical users. This approach has many unique advantages:
+Instead of using a predefined "one-size-fits-all" data model to store your content, Directus
+"mirrors" your actual SQL database in real-time. The principle is akin to a database client (eg:
+_phpMyAdmin_), but includes far mor advanced tools, and is safe and intuitive enough for
+non-technical users. This approach has many unique advantages:
 
 -   A custom SQL database schema, tailored to your exact requirements
 -   Significant performance improvements through optimizations and indexing
@@ -14,7 +18,10 @@ Instead of using a predefined "one-size-fits-all" data model to store your conte
 
 ## Directus API
 
-The Directus API uses _Database Mirroring_ to dynamically generate REST endpoints and a GraphQL schema based on the connected database's architecture. It is written in [Node.js](https://nodejs.org) and uses database abstraction to support most [SQL database vendors](/guides/installation#databases).
+The Directus API uses _Database Mirroring_ to dynamically generate REST endpoints and a GraphQL
+schema based on the connected database's architecture. It is written in
+[Node.js](https://nodejs.org) and uses database abstraction to support most
+[SQL database vendors](/guides/installation#databases).
 
 ### Relevant Docs
 
@@ -23,7 +30,9 @@ The Directus API uses _Database Mirroring_ to dynamically generate REST endpoint
 
 ## Directus App
 
-The Directus App is decoupled from, and powered by, the Directus API. It provides a way for both technical admins and non-technical users to view and manage content of the connected database. It is written in [Vue.js](https://vuejs.org) v3, is completely modular, and is highly customizable.
+The Directus App is decoupled from, and powered by, the Directus API. It provides a way for both
+technical admins and non-technical users to view and manage content of the connected database. It is
+written in [Vue.js](https://vuejs.org) v3, is completely modular, and is highly customizable.
 
 ### Relevant Docs
 
@@ -32,7 +41,10 @@ The Directus App is decoupled from, and powered by, the Directus API. It provide
 
 ## Projects & Environments
 
-A Project is a complete instance of Directus. Each project primarily represents a database, but also includes a configuration file and any related asset storage. This modular approach means you can also create different environments (eg: Dev, Staging, Prod) by simply creating additional project instances.
+A Project is a complete instance of Directus. Each project primarily represents a database, but also
+includes a configuration file and any related asset storage. This modular approach means you can
+also create different environments (eg: Dev, Staging, Prod) by simply creating additional project
+instances.
 
 <!-- ::: tip Migrating Environments
 Directus includes [Export](#), [Import](#), [Backup](#), and [Restore](#) features to assist with custom migration workflows between environments. You can also roll your own process by copying the database and assets between environments, either manually or via an automated script.
@@ -42,11 +54,17 @@ Directus includes [Export](#), [Import](#), [Backup](#), and [Restore](#) featur
 
 ## Collections
 
-A Collection is a grouping of similar Items. Each collection represents a table in your database. Directus automatically uses a built-in [title formatter](/concepts/app-extensions) to display your database table names prettified, and you can use [translations](/concepts/data-model) to completely rename them if needed.
+A Collection is a grouping of similar Items. Each collection represents a table in your database.
+Directus automatically uses a built-in [title formatter](/concepts/app-extensions) to display your
+database table names prettified, and you can use [translations](/concepts/data-model) to completely
+rename them if needed.
 
-::: tip Usage
-Collections can be organized in any way that is appropriate for your project. You can architect them platform-specific (eg: _pages_ of a website), or in a more platform-agnostic way (eg: raw _customers_ of your business). While there's no right or wrong way to structure your data-model, we recommend keeping your data as agnostic as possible so it is easier to repurpose in the future. In short, **learn to see your data as its own asset — not only through the lens of your immediate project needs**.
-:::
+::: tip Usage Collections can be organized in any way that is appropriate for your project. You can
+architect them platform-specific (eg: _pages_ of a website), or in a more platform-agnostic way (eg:
+raw _customers_ of your business). While there's no right or wrong way to structure your data-model,
+we recommend keeping your data as agnostic as possible so it is easier to repurpose in the future.
+In short, **learn to see your data as its own asset — not only through the lens of your immediate
+project needs**. :::
 
 ### Relevant Guides
 
@@ -55,7 +73,9 @@ Collections can be organized in any way that is appropriate for your project. Yo
 
 ## Presets
 
-Presets store the exact state of a [collection detail](/concepts/app-overview) page. These are used to set layout defaults for a user, or to define bookmarks that can be used to quickly recall specific datasets.
+Presets store the exact state of a [collection detail](/concepts/app-overview) page. These are used
+to set layout defaults for a user, or to define bookmarks that can be used to quickly recall
+specific datasets.
 
 ### Relevant Guides
 
@@ -64,21 +84,25 @@ Presets store the exact state of a [collection detail](/concepts/app-overview) p
 
 ## Fields
 
-A Field is a specific type of value within a Collection. Each field represents a database column. Directus automatically uses a built-in [title formatter](/concepts/app-extensions#title-formatter) to display your database column names prettified, and you can use [translations](/guides/fields) to completely rename them if needed.
+A Field is a specific type of value within a Collection. Each field represents a database column.
+Directus automatically uses a built-in [title formatter](/concepts/app-extensions#title-formatter)
+to display your database column names prettified, and you can use [translations](/guides/fields) to
+completely rename them if needed.
 
-Each field also mirrors other characteristics from the column, including its `type`, `default`, `length`, `allow_null`, etc.
+Each field also mirrors other characteristics from the column, including its `type`, `default`,
+`length`, `allow_null`, etc.
 
-::: tip Usage
-You might have `title`, `body`, `author`, and `date_published` fields within an `articles` collection.
-:::
+::: tip Usage You might have `title`, `body`, `author`, and `date_published` fields within an
+`articles` collection. :::
 
-::: tip Aliases
-Not all fields in Directus map directly to an actual database column within their table. Some relational fields, like One-to-Many (O2M) and Many-to-Many (M2M), represent data that is stored in different tables. Other fields are only for presentation and don't save data at all, such as a divider. These are called "alias" fields.
-:::
+::: tip Aliases Not all fields in Directus map directly to an actual database column within their
+table. Some relational fields, like One-to-Many (O2M) and Many-to-Many (M2M), represent data that is
+stored in different tables. Other fields are only for presentation and don't save data at all, such
+as a divider. These are called "alias" fields. :::
 
-::: tip Relational Fields
-Fields that reference other items (in the same collection or different) are called relational fields. Linking or connecting data relationally is an immensely powerful feature of relational databases and SQL queries.
-:::
+::: tip Relational Fields Fields that reference other items (in the same collection or different)
+are called relational fields. Linking or connecting data relationally is an immensely powerful
+feature of relational databases and SQL queries. :::
 
 ### Relevant Guides
 
@@ -95,7 +119,9 @@ Fields that reference other items (in the same collection or different) are call
 
 ## Types
 
-Directus has built-in database abstraction for managing all SQL database vendors. However, each of those vendors has a different list of supported column datatypes. To standardize all of these differences, Directus has a single superset of types that each map to the more specific vendor ones.
+Directus has built-in database abstraction for managing all SQL database vendors. However, each of
+those vendors has a different list of supported column datatypes. To standardize all of these
+differences, Directus has a single superset of types that each map to the more specific vendor ones.
 
 -   String
 -   Text
@@ -116,7 +142,8 @@ Directus has built-in database abstraction for managing all SQL database vendors
 
 ## Items
 
-An Item is an object containing the field values within a Collection. Each item represents a database record. Similar to a "row" within a spreadsheet.
+An Item is an object containing the field values within a Collection. Each item represents a
+database record. Similar to a "row" within a spreadsheet.
 
 ### Relevant Guides
 
diff --git a/docs/concepts/relationships.md b/docs/concepts/relationships.md
index 05dfbaaefa..d205279bf7 100644
--- a/docs/concepts/relationships.md
+++ b/docs/concepts/relationships.md
@@ -1,28 +1,41 @@
 # Relationships
 
-> As you might have guessed, relationships are a crucial part of any relational database. Directus supports all standard relationship types, as well as a few more _compound_ types that offer greater flexibility.
+> As you might have guessed, relationships are a crucial part of any relational database. Directus
+> supports all standard relationship types, as well as a few more _compound_ types that offer
+> greater flexibility.
 
 ## Understanding Relationships
 
-While it may seem complex at first, relational data is actually quite straightforward once you understand what's happening behind the confusing terminology. Before diving into the details of each type, let's first cover a few basics that will help you better visualize each in your mind's eye.
+While it may seem complex at first, relational data is actually quite straightforward once you
+understand what's happening behind the confusing terminology. Before diving into the details of each
+type, let's first cover a few basics that will help you better visualize each in your mind's eye.
 
 ### PKs vs FKs
 
-Every [item](#) in a relational database has a unique "key" that identifies it within its [collection](#). Because it's required, the key is the first [field](#) created within a collection, typically storing an "auto-increment" number, an automatically generated unique hash, or a manually entered value. They are often abbreviated to "PK" (Primary Key), "ID" (Identifier), "UID" (Unique Identifier), or "UUID" (Universally Unique Identifier), depending on the type of value they store. After it's created, the value of an item's PK should _never_ change.
+Every [item](#) in a relational database has a unique "key" that identifies it within its
+[collection](#). Because it's required, the key is the first [field](#) created within a collection,
+typically storing an "auto-increment" number, an automatically generated unique hash, or a manually
+entered value. They are often abbreviated to "PK" (Primary Key), "ID" (Identifier), "UID" (Unique
+Identifier), or "UUID" (Universally Unique Identifier), depending on the type of value they store.
+After it's created, the value of an item's PK should _never_ change.
 
-To link items together relationally, you simply save a reference of an item's PK in a different field. That _reference_ is called a Foreign Key (FK).
+To link items together relationally, you simply save a reference of an item's PK in a different
+field. That _reference_ is called a Foreign Key (FK).
 
-::: Compound Keys
-We've ignored compound keys in this explanation to help keep things as simple as possible.
-:::
+::: Compound Keys We've ignored compound keys in this explanation to help keep things as simple as
+possible. :::
 
 ### Perspective Matters
 
-Just like primary and foreign keys are directional, relationships are always relative to their "parent" collection. Looking at the same relationship/key from the perspective of a different collection may change or reverse its type.
+Just like primary and foreign keys are directional, relationships are always relative to their
+"parent" collection. Looking at the same relationship/key from the perspective of a different
+collection may change or reverse its type.
 
 ## Many-to-One (M2O)
 
-A Many-to-One (M2O) relationship exists on a field that saves a single FK. For example, a _city_ can only be in one _country_, but a _country_ can have many _cities_. So the M2O data model would look like this:
+A Many-to-One (M2O) relationship exists on a field that saves a single FK. For example, a _city_ can
+only be in one _country_, but a _country_ can have many _cities_. So the M2O data model would look
+like this:
 
 ```
 cities ("Many" Collection)
@@ -37,7 +50,10 @@ country ("One" Collection)
 
 ## One-to-Many (O2M)
 
-A One-to-Many (O2M) relationship uses an [alias](#) field to reference one or more FKs in a M2O. This is the _exact same_ relationship as the M2O above, but looking at it from the opposite perspective (see [Perspective Matters](#)). So the O2M data model is the same, but adds an alias "cities" field to the Country collection, like this:
+A One-to-Many (O2M) relationship uses an [alias](#) field to reference one or more FKs in a M2O.
+This is the _exact same_ relationship as the M2O above, but looking at it from the opposite
+perspective (see [Perspective Matters](#)). So the O2M data model is the same, but adds an alias
+"cities" field to the Country collection, like this:
 
 ```
 country ("One" Collection)
@@ -51,17 +67,18 @@ cities ("Many" Collection)
 - country (stores the FK to a country)
 ```
 
-::: Manual Reordering
-To enable manual reordering for a O2M, simply add a field with the `sort` type to the "many" side (`cities` in the above example).
-:::
+::: Manual Reordering To enable manual reordering for a O2M, simply add a field with the `sort` type
+to the "many" side (`cities` in the above example). :::
 
-::: Translations
-The Translations interface allows [creating multilingual content](#) relationally. It is a standard O2M relatinship, but also includes an additional field on the "many" collection to hold the language key
-:::
+::: Translations The Translations interface allows [creating multilingual content](#) relationally.
+It is a standard O2M relatinship, but also includes an additional field on the "many" collection to
+hold the language key :::
 
 ## Many-to-Many (M2M)
 
-A Many-to-Many (M2M) relationship uses a "Junction Table" to connect many items from one collection, to many items of another collection. For example, a _recipe_ can have many _ingredients_, and _ingredients_ can be in many _recipes_. So the M2M data model would look like this:
+A Many-to-Many (M2M) relationship uses a "Junction Table" to connect many items from one collection,
+to many items of another collection. For example, a _recipe_ can have many _ingredients_, and
+_ingredients_ can be in many _recipes_. So the M2M data model would look like this:
 
 ```
 recipes (Collection)
@@ -81,31 +98,42 @@ recipe_ingredients (Junction Collection)
 - quantity
 ```
 
-Notice that the example above also has a `quantity` field on the junction table. You can add any contextual fields to the junction, and they will also be included in the App's relational edit form.
+Notice that the example above also has a `quantity` field on the junction table. You can add any
+contextual fields to the junction, and they will also be included in the App's relational edit form.
 
-:::warning M2M == O2M x2
-An M2M is technically two relationships viewed as one. Each side has a O2M to the Junction Table that sits in the middle. In that sense, there really is no "M2M".
-:::
+:::warning M2M == O2M x2 An M2M is technically two relationships viewed as one. Each side has a O2M
+to the Junction Table that sits in the middle. In that sense, there really is no "M2M". :::
 
-::: Manual Reordering
-To enable manual reordering for a M2M, simply add a numeric field to the junction table and set it as the [Collection Sort](#).
-:::
+::: Manual Reordering To enable manual reordering for a M2M, simply add a numeric field to the
+junction table and set it as the [Collection Sort](#). :::
 
-::: Self-Referencing
-You can also have a M2M relationship that connects items within the _same_ collection. A common example of this is "Related Articles", where each article might relate to many other articles.
-:::
+::: Self-Referencing You can also have a M2M relationship that connects items within the _same_
+collection. A common example of this is "Related Articles", where each article might relate to many
+other articles. :::
 
 ## One-to-One (O2O)
 
-Directus does not include a one-to-one (O2O) relationship type or interface. However a O2O saves is essentially the same as a M2O (storing a foreign key). The only difference is that a O2O enforces the cardinality. In other words, selecting a relational item in a O2O means that item can not be selected elsewhere (it can only be used once). This functionality can be added by checking and constraining uniqueness via a [custom event hook](#) or [custom interface](#).
+Directus does not include a one-to-one (O2O) relationship type or interface. However a O2O saves is
+essentially the same as a M2O (storing a foreign key). The only difference is that a O2O enforces
+the cardinality. In other words, selecting a relational item in a O2O means that item can not be
+selected elsewhere (it can only be used once). This functionality can be added by checking and
+constraining uniqueness via a [custom event hook](#) or [custom interface](#).
 
-An example of a O2O is: a _person_ only has one unique set of _fingerprints_, and those _fingerprints_ only belong to one _person_.
+An example of a O2O is: a _person_ only has one unique set of _fingerprints_, and those
+_fingerprints_ only belong to one _person_.
 
 ## Many-to-Any (M2X)
 
-Sometimes called a "matrix field" or "replicator", the Many-to-Any (M2X) relationship is essentially the same as a M2M, but with one crucial difference: the junction table also stores the _parent collection name of the FK_. This "compound key" combines the collection name and FK to provide a unique reference to _any_ other item within the project. You can then artificially limit which collections are valid through an "allow list".
+Sometimes called a "matrix field" or "replicator", the Many-to-Any (M2X) relationship is essentially
+the same as a M2M, but with one crucial difference: the junction table also stores the _parent
+collection name of the FK_. This "compound key" combines the collection name and FK to provide a
+unique reference to _any_ other item within the project. You can then artificially limit which
+collections are valid through an "allow list".
 
-An example of a M2X is a "page layout builder". These typically will have modular components across several different collections (eg: "Heading", "Text Block", "Media Asset", etc), and a _Pages_ collections where you can piece them together. Therefore, the junction table will link a specific page with specific components, allowing the creation of relational page layouts.
+An example of a M2X is a "page layout builder". These typically will have modular components across
+several different collections (eg: "Heading", "Text Block", "Media Asset", etc), and a _Pages_
+collections where you can piece them together. Therefore, the junction table will link a specific
+page with specific components, allowing the creation of relational page layouts.
 
 ---
 
diff --git a/docs/concepts/users-roles-and-permissions.md b/docs/concepts/users-roles-and-permissions.md
index 455bdf35b7..178fa8853c 100644
--- a/docs/concepts/users-roles-and-permissions.md
+++ b/docs/concepts/users-roles-and-permissions.md
@@ -1,45 +1,56 @@
 # Users, Roles & Permissions
 
-> Directus Users are the individual accounts that let you authenticate into the API and App. Each user belongs to a Role which defines its granular Permissions.
+> Directus Users are the individual accounts that let you authenticate into the API and App. Each
+> user belongs to a Role which defines its granular Permissions.
 
 ## Users
 
-To use the App or API, you'll need a valid Directus User. Each user is assigned to a role that determines what they have access to see and do. For instance, some users have access to the App, while others can only connect to the API. Directus ships with a number of profile fields that help create a full-featured [User Directory](#), and setting fields that allow customizing your experience.
+To use the App or API, you'll need a valid Directus User. Each user is assigned to a role that
+determines what they have access to see and do. For instance, some users have access to the App,
+while others can only connect to the API. Directus ships with a number of profile fields that help
+create a full-featured [User Directory](#), and setting fields that allow customizing your
+experience.
 
 All Directus users are aggregated and shown on the [User Directory](#) page of the App
 
-::: Extending Directus Users
-While the included fields within Directus Users are required/locked, you can still _extend_ this collection with additional custom fields as needed. You can do this via the normal [Create a new Field](#) process from within the system collection.
-:::
+::: Extending Directus Users While the included fields within Directus Users are required/locked,
+you can still _extend_ this collection with additional custom fields as needed. You can do this via
+the normal [Create a new Field](#) process from within the system collection. :::
 
-::: System vs Custom Users
-If your project requires a users, members, customers, etc., we recommend creating your own collection to manage these instead of trying to repurpose the Directus Users system.
-:::
+::: System vs Custom Users If your project requires a users, members, customers, etc., we recommend
+creating your own collection to manage these instead of trying to repurpose the Directus Users
+system. :::
 
 ### Relevant Guides
 
-* [Setting up your User Profile](#)
-* [Inviting a User](#)
-* [Creating a User](#)
-* [Archiving a User](#)
-* [Deleting a User](#)
+-   [Setting up your User Profile](#)
+-   [Inviting a User](#)
+-   [Creating a User](#)
+-   [Archiving a User](#)
+-   [Deleting a User](#)
 
 ## Roles
 
-Each user is assigned to one Role, which determines their permissions within the App and API. There is no limit to the number of roles you can create within Directus, so feel free to organize your users in whatever way feels most appropriate.
+Each user is assigned to one Role, which determines their permissions within the App and API. There
+is no limit to the number of roles you can create within Directus, so feel free to organize your
+users in whatever way feels most appropriate.
 
 ### Public Role
 
-Public is not technically a role, and can't be found in the `directus_roles` table. Instead, it represents the _lack_ of a role, providing a place to configure permissions for unauthenticated users. This role can not be deleted, and has no permissions by default.
+Public is not technically a role, and can't be found in the `directus_roles` table. Instead, it
+represents the _lack_ of a role, providing a place to configure permissions for unauthenticated
+users. This role can not be deleted, and has no permissions by default.
 
 ### Administrators Role
 
-Upon installation, Directus automatically creates this initial role to grant access to the first admin user. It is just a normal role, and like any other it can be updated, renamed or deleted, however your project must maintain at least one role with [Admin Access](#) at all times.
+Upon installation, Directus automatically creates this initial role to grant access to the first
+admin user. It is just a normal role, and like any other it can be updated, renamed or deleted,
+however your project must maintain at least one role with [Admin Access](#) at all times.
 
 ### Relevant Guides
 
-* [Creating a Role](#)
-* [Deleting a Role](#)
+-   [Creating a Role](#)
+-   [Deleting a Role](#)
 
 ## Permissions
 
@@ -47,4 +58,4 @@ Directus gives you granular, filter-based permissions for managing access-contro
 
 ### Relevant Guides
 
-* [Managing Permissions](#)
+-   [Managing Permissions](#)
diff --git a/docs/getting-started/backing-directus.md b/docs/getting-started/backing-directus.md
index 5876658140..25821d9b56 100644
--- a/docs/getting-started/backing-directus.md
+++ b/docs/getting-started/backing-directus.md
@@ -1,26 +1,36 @@
 # Backing Directus
 
-> Directus is both _premium_ and _free_ — two things that don't often go together. It takes significant resources to maintain and advance the platform. If you'd like to help keep Directus active and open-source please consider supporting it through one of the methods below.
+> Directus is both _premium_ and _free_ — two things that don't often go together. It takes
+> significant resources to maintain and advance the platform. If you'd like to help keep Directus
+> active and open-source please consider supporting it through one of the methods below.
 
 ## Financial Support
 
-Talented full-time and part-time staff, infrastructure, and third-party services are just some of our organization's expenses, and revenue from our Cloud services and donations from sponsors dosen't fully cover those costs. Below are a few ways to help us keep the lights on and move towards self-sufficiency.
+Talented full-time and part-time staff, infrastructure, and third-party services are just some of
+our organization's expenses, and revenue from our Cloud services and donations from sponsors dosen't
+fully cover those costs. Below are a few ways to help us keep the lights on and move towards
+self-sufficiency.
 
 ### GitHub Sponsors
 
-Monthly donations via [GitHub Sponsors](#) are the most reliable form of financial support, and donations made directly to our core developers are currently **doubled** by GitHub's matching program!
+Monthly donations via [GitHub Sponsors](#) are the most reliable form of financial support, and
+donations made directly to our core developers are currently **doubled** by GitHub's matching
+program!
 
-* [rijkvanzanten](https://github.com/rijkvanzanten) — Technical Lead
-* [WoLfulus](https://github.com/WoLfulus) — DevOps
-* [Nitwel](https://github.com/Nitwel) — Developer
+-   [rijkvanzanten](https://github.com/rijkvanzanten) — Technical Lead
+-   [WoLfulus](https://github.com/WoLfulus) — DevOps
+-   [Nitwel](https://github.com/Nitwel) — Developer
 
 ### Sponsored Work
 
-[Commissioned Features](#) and [Expedited Fixes](#) are great ways to financially support the development of Directus, and improve the codebase for the community.
+[Commissioned Features](#) and [Expedited Fixes](#) are great ways to financially support the
+development of Directus, and improve the codebase for the community.
 
 ### Merch
 
-Our merchandise is a great way to support Directus — you get some swag, and we get some financial support and advertising. Simply make an appropriate financial donation through [GitHub Sponsors](#), message us with sizing/shipping details, and we'll get it shipped!
+Our merchandise is a great way to support Directus — you get some swag, and we get some financial
+support and advertising. Simply make an appropriate financial donation through [GitHub Sponsors](#),
+message us with sizing/shipping details, and we'll get it shipped!
 
 ## Other Contributions
 
@@ -28,20 +38,30 @@ Below are several ways anyone can help improve our ecosystem.
 
 ### Code Pull Requests
 
-Squashing bugs, optimizing the codebase, increasing test coverage, and adding new features, are all extremely valuable. Not technical? We have plenty of documentation that can always use some extra attention. Learn more in our [Contributors Guide](#).
+Squashing bugs, optimizing the codebase, increasing test coverage, and adding new features, are all
+extremely valuable. Not technical? We have plenty of documentation that can always use some extra
+attention. Learn more in our [Contributors Guide](#).
 
 ### Translations
 
-Every translation enables users in new languages to use our international platform. Our [Crowdin integration](#) makes polishing existing translations or creating new ones a breeze.
+Every translation enables users in new languages to use our international platform. Our
+[Crowdin integration](#) makes polishing existing translations or creating new ones a breeze.
 
 ### Bug Reporting
 
-If you encounter an issue within Directus, no matter how small, we would love to hear about it. Proper bug reporing helps our team assess the platform's stability. [Report a bug](#)
+If you encounter an issue within Directus, no matter how small, we would love to hear about it.
+Proper bug reporing helps our team assess the platform's stability. [Report a bug](#)
 
 ### Brand Advocacy
 
-You can create _perfect_ software, but if no one knows about it, it's all for naught. Marketing and advertising are expensive, but you can help us avoid these costs with the following quick options:
+You can create _perfect_ software, but if no one knows about it, it's all for naught. Marketing and
+advertising are expensive, but you can help us avoid these costs with the following quick options:
 
-* **GitHub Stars** — The primary metric by which we measure our success. It only takes five seconds to head to [directus/directus](#) and click the star — enough in a short period of time and Directus gets featured on GitHub's trending page!
-* **Social Posts** — A quick post mentioning [@directus](https://twitter.com/directus) goes a long way, and we re-tweet the team's favorite shout-outs to our 30K+ followers.
-* **Testimonials** — _One sentence._ Even that was a sentence, and it was only two words! If you're a fan of Directus, we'd love to hear why with a short endorsement. Shoot us an [email](#), [Tweet](#), or [Discord](#) message with your name, title, and company.
+-   **GitHub Stars** — The primary metric by which we measure our success. It only takes five
+    seconds to head to [directus/directus](#) and click the star — enough in a short period of time
+    and Directus gets featured on GitHub's trending page!
+-   **Social Posts** — A quick post mentioning [@directus](https://twitter.com/directus) goes a long
+    way, and we re-tweet the team's favorite shout-outs to our 30K+ followers.
+-   **Testimonials** — _One sentence._ Even that was a sentence, and it was only two words! If
+    you're a fan of Directus, we'd love to hear why with a short endorsement. Shoot us an
+    [email](#), [Tweet](#), or [Discord](#) message with your name, title, and company.
diff --git a/docs/getting-started/contributing.md b/docs/getting-started/contributing.md
index c378581236..714be83717 100644
--- a/docs/getting-started/contributing.md
+++ b/docs/getting-started/contributing.md
@@ -1,32 +1,48 @@
 # Contributing
 
-> Our team truly appreciates every single pull-request, bug report, and feature request made by our community. If you have _any_ questions along the way, please reach out to our Core team on [Discord](https://directus.chat).
+> Our team truly appreciates every single pull-request, bug report, and feature request made by our
+> community. If you have _any_ questions along the way, please reach out to our Core team on
+> [Discord](https://directus.chat).
 
 ## Node Monorepo
 
-Our Node.js repository is located at `directus/directus` and houses the Admin App (vue.js 3), Node.js API, project documentation (markdown), and API Specification (OpenAPI). Directus follows a monorepo design similar to React or Babel — to learn more about our monorepo's design and structure, see our [Codebase Overview](#) below.
+Our Node.js repository is located at `directus/directus` and houses the Admin App (vue.js 3),
+Node.js API, project documentation (markdown), and API Specification (OpenAPI). Directus follows a
+monorepo design similar to React or Babel — to learn more about our monorepo's design and structure,
+see our [Codebase Overview](#) below.
 
-To contribute to the project, please follow the instructions located within our GitHub repoitory's [contributing.md file](#).
+To contribute to the project, please follow the instructions located within our GitHub repoitory's
+[contributing.md file](#).
 
-::: tip PHP API Port
-While the Node.js version of Directus defines the official specification and is our team's primary focus, we also support a community-lead PHP API port in Laravel. This secondary codebase is located in a separate git repository at [`directus/php`](#).
-:::
+::: tip PHP API Port While the Node.js version of Directus defines the official specification and is
+our team's primary focus, we also support a community-lead PHP API port in Laravel. This secondary
+codebase is located in a separate git repository at [`directus/php`](#). :::
 
 ## Feature Requests
 
-Feature requests are a great way to let our team know what should be prioritized next. You can [submit a feature request](https://github.com/directus/directus/discussions/category_choices) or upvote [existing submissions](https://github.com/directus/directus/discussions) all via our GitHub Discussions board.
+Feature requests are a great way to let our team know what should be prioritized next. You can
+[submit a feature request](https://github.com/directus/directus/discussions/category_choices) or
+upvote [existing submissions](https://github.com/directus/directus/discussions) all via our GitHub
+Discussions board.
 
-::: warning The 80/20 Rule
-To keep the Directus codebase as clean and simple as possible, we will only consider approving features that we feel at least 80% of our user-base will find valuable. If your feature request falls within the 20% range, it is considered an edge-case and should be implemented as an extension.
-:::
+::: warning The 80/20 Rule To keep the Directus codebase as clean and simple as possible, we will
+only consider approving features that we feel at least 80% of our user-base will find valuable. If
+your feature request falls within the 20% range, it is considered an edge-case and should be
+implemented as an extension. :::
 
 ## RFCs
 
-Some Directus features/fixes may require additional design, strategy, and/or discussion before beginning work. For these notable pull-requests, you should first submit an RFC (Request For Comments) to our core team via [Discord](https://directus.chat). This process is relatively informal, but ensures proper alignment, and helps avoid squandered development time by contributors.
+Some Directus features/fixes may require additional design, strategy, and/or discussion before
+beginning work. For these notable pull-requests, you should first submit an RFC (Request For
+Comments) to our core team via [Discord](https://directus.chat). This process is relatively
+informal, but ensures proper alignment, and helps avoid squandered development time by contributors.
 
 ## Bug Reporting
 
-Reporting any bugs you come across is an invaluable part of helping keep Directus stable. After confirming a similar issue doesn't already exist, you can [submit a bug report](https://github.com/directus/directus/issues/new) via GitHub Issues. Please ensure the following for all submissions:
+Reporting any bugs you come across is an invaluable part of helping keep Directus stable. After
+confirming a similar issue doesn't already exist, you can
+[submit a bug report](https://github.com/directus/directus/issues/new) via GitHub Issues. Please
+ensure the following for all submissions:
 
 -   You are experiencing an actual bug, not a configuration issue
 -   You are not asking a question or requesting a new feature
@@ -41,20 +57,30 @@ Reporting any bugs you come across is an invaluable part of helping keep Directu
 
 ## Reporting Security Vulnerabilities
 
-If you believe you have discovered a security issue within a Directus product or service, please reach out to us directly over email: [support@directus.io](mailto:support@directus.io). We will then open a [GitHub Security Advisory](https://github.com/directus/directus/security/advisories) for tracking the fix.
+If you believe you have discovered a security issue within a Directus product or service, please
+reach out to us directly over email: [support@directus.io](mailto:support@directus.io). We will then
+open a [GitHub Security Advisory](https://github.com/directus/directus/security/advisories) for
+tracking the fix.
 
-We value the members of the independent security research community who find security vulnerabilities and work with our team so that proper fixes can be issued to users. Our policy is to credit all researchers in the fix's release notes. In order to receive credit, security researchers must follow responsible disclosure practices, including:
+We value the members of the independent security research community who find security
+vulnerabilities and work with our team so that proper fixes can be issued to users. Our policy is to
+credit all researchers in the fix's release notes. In order to receive credit, security researchers
+must follow responsible disclosure practices, including:
 
 -   They do not publish the vulnerability prior to the Directus team releasing a fix for it
--   They do not divulge exact details of the issue, for example, through exploits or proof-of-concepts
+-   They do not divulge exact details of the issue, for example, through exploits or
+    proof-of-concepts
 
 ## Code of Conduct
 
-The Directus [Code of Conduct](https://github.com/directus/directus/blob/main/code_of_conduct.md) is one of the ways we put our values into practice. We expect all of our staff, contractors and contributors to know and follow this code.
+The Directus [Code of Conduct](https://github.com/directus/directus/blob/main/code_of_conduct.md) is
+one of the ways we put our values into practice. We expect all of our staff, contractors and
+contributors to know and follow this code.
 
 ## Development Workflow
 
-Before getting started, ensure you your local environment meets our [minimum requirements](/guides/installation/cli) and you are familiar with Git.
+Before getting started, ensure you your local environment meets our
+[minimum requirements](/guides/installation/cli) and you are familiar with Git.
 
 ### 1. Fork the Directus repository
 
@@ -80,7 +106,9 @@ npm install
 
 ### 5. Setup the Database & Env File
 
-For this step, you'll need to already have a SQL database up-and-running, otherwise you can only use the SQLite driver, which will create the database for you. Run the following command from within root of the project:
+For this step, you'll need to already have a SQL database up-and-running, otherwise you can only use
+the SQLite driver, which will create the database for you. Run the following command from within
+root of the project:
 
 ```bash
 npm run cli -- init
@@ -96,7 +124,8 @@ npm run dev
 
 ### 7. Make your fixes/changes
 
-At this point you are ready to start working on Directus! Before diving in however, it's worth reading through our docs on [submitting a pull-request](#Submitting-a-Pull-Request).
+At this point you are ready to start working on Directus! Before diving in however, it's worth
+reading through our docs on [submitting a pull-request](#Submitting-a-Pull-Request).
 
 ## Submitting a Pull-Request
 
@@ -106,7 +135,8 @@ Please read our docs on the [RFC process](#rfcs).
 
 ### 2. Update relevant docs
 
-Before submitting any pull-requests, ensure that any relevant documentation (included in this same repo) is updated.
+Before submitting any pull-requests, ensure that any relevant documentation (included in this same
+repo) is updated.
 
 ### 3. Push your changes
 
@@ -116,9 +146,12 @@ git push -u origin YOUR-BRANCH-NAME
 
 ### Submit a pull-request
 
-Once you push the changes to your repo, the "Compare & pull request" button will appear in GitHub. Click it and you'll be taken to a screen where you can fill in the appropriate details. Finally, open the pull request by clicking the "Create pull request" button.
+Once you push the changes to your repo, the "Compare & pull request" button will appear in GitHub.
+Click it and you'll be taken to a screen where you can fill in the appropriate details. Finally,
+open the pull request by clicking the "Create pull request" button.
 
-Now our core staff will review your contribution and either merge it, or request that you to make changes.
+Now our core staff will review your contribution and either merge it, or request that you to make
+changes.
 
 ## Codebase Overview
 
diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md
index 7d70dcb0be..1582ea7d36 100644
--- a/docs/getting-started/installation.md
+++ b/docs/getting-started/installation.md
@@ -1,26 +1,27 @@
 # Installation
 
-Directus can be installed in many different ways, on several different stacks. CLI is the recommended method, but there are many ways to get started with our platform depending on your needs.
+Directus can be installed in many different ways, on several different stacks. CLI is the
+recommended method, but there are many ways to get started with our platform depending on your
+needs.
 
-* [Command Line Interface (CLI)](/guides/installation/cli.md)
-* [Docker](/guides/installation/docker.md)
-* [Manually](/guides/installation/manual.md)
+-   [Command Line Interface (CLI)](/guides/installation/cli.md)
+-   [Docker](/guides/installation/docker.md)
+-   [Manually](/guides/installation/manual.md)
 
-::: tip Development Environment
-Developers looking to work on the project's source code should follow our [Contributing Guide](/getting-started/contributing).
-:::
+::: tip Development Environment Developers looking to work on the project's source code should
+follow our [Contributing Guide](/getting-started/contributing). :::
 
 ## Deployment Guides
 
-* [Amazon AWS](#)
-* [DigitalOcean Droplet](#)
-* [DigitalOcean One-Click](/guides/installation/digitalocean-one-click.md)
-* [Google App Engine](#)
-* [Heroku](/guides/installation/heroku.md)
-* [Microsoft Azure](#)
+-   [Amazon AWS](#)
+-   [DigitalOcean Droplet](#)
+-   [DigitalOcean One-Click](/guides/installation/digitalocean-one-click.md)
+-   [Google App Engine](#)
+-   [Heroku](/guides/installation/heroku.md)
+-   [Microsoft Azure](#)
 
 ## Optional Setup Guides
 
-* [Caddy](#)
-* [Nginx](#)
-* [HAProxy](#)
+-   [Caddy](#)
+-   [Nginx](#)
+-   [HAProxy](#)
diff --git a/docs/getting-started/introduction.md b/docs/getting-started/introduction.md
index fe81b26061..8da3f7fb34 100644
--- a/docs/getting-started/introduction.md
+++ b/docs/getting-started/introduction.md
@@ -1,56 +1,81 @@
 # 🐰 Welcome to the Directus Docs!
 
-> These Docs will help get you up-and-running quickly, guide you through advanced features, and explain the concepts that make Directus so unique.
+> These Docs will help get you up-and-running quickly, guide you through advanced features, and
+> explain the concepts that make Directus so unique.
 
 ## What is Directus?
 
-**Directus is an open-source platform that provides a real-time API and intuitive Admin App for your custom database.** Built on node.js and vue.js 3, it allows both administrators and non-technical users to view and manage the content/data stored within pure SQL databases. It can be used as a headless CMS for managing project content, a database client for modeling and viewing raw data, or as a standalone customizable WebApp.
+**Directus is an open-source platform that provides a real-time API and intuitive Admin App for your
+custom database.** Built on node.js and vue.js 3, it allows both administrators and non-technical
+users to view and manage the content/data stored within pure SQL databases. It can be used as a
+headless CMS for managing project content, a database client for modeling and viewing raw data, or
+as a standalone customizable WebApp.
 
-::: details What's in a name?
-Directus ([duh REKT iss](http://audio.pronouncekiwi.com/Salli/Directus)) is latin for: _laid straight, arranged in lines_. The broadest goal of Directus is to present data in a simple, orderly, and intuitive way.
-:::
+::: details What's in a name? Directus
+([duh REKT iss](http://audio.pronouncekiwi.com/Salli/Directus)) is latin for: _laid straight,
+arranged in lines_. The broadest goal of Directus is to present data in a simple, orderly, and
+intuitive way. :::
 
 ## What makes it unique?
 
-**Directus dynamically generates custom API endpoints based on your SQL database's custom schema in real-time — something we call "Database Mirroring".** Whether you install fresh or on top of an existing database, you always maintain complete control over your actual database... including tables, columns, datatypes, default values, indexes, relationships, etc.
+**Directus dynamically generates custom API endpoints based on your SQL database's custom schema in
+real-time — something we call "Database Mirroring".** Whether you install fresh or on top of an
+existing database, you always maintain complete control over your actual database... including
+tables, columns, datatypes, default values, indexes, relationships, etc.
 
-Perhaps one of the biggest advantages of _Database Mirroring_ is that you have direct access to your pure and unaltered data. That means you can even bypass the Directus middleware (API, SDK, App), and connect to your data with proper SQL queries — effectively removing all bottlenecks, additional latency, or proprietary access limitations.
+Perhaps one of the biggest advantages of _Database Mirroring_ is that you have direct access to your
+pure and unaltered data. That means you can even bypass the Directus middleware (API, SDK, App), and
+connect to your data with proper SQL queries — effectively removing all bottlenecks, additional
+latency, or proprietary access limitations.
 
-Directus is a simple solution for complex problems. Every aspect of Directus is data-first and guided by the following core principles:
+Directus is a simple solution for complex problems. Every aspect of Directus is data-first and
+guided by the following core principles:
 
-* **Pure** — There is no predefined model or proprietary rules for your agnostic schema, and all system settings are stored separately.
-* **Open** — Our entire codebase is public and transparent, allowing for end-to-end audits. Nothing is obfuscated or black-boxed.
-* **Portable** — Data is stored in your bespoke database and can be migrated/exported/backed-up at any time. Absolutely no vendor lock-in.
-* **Limitless** — Create unlimited users, roles, languages, collections, and items. No arbitrary restrictions or paywall limitations.
-* **Extensible** — Every aspect of the platform is modular, allowing you to adapt, customize, and infinitely extend the Core engine.
-* **Unopinionated** — Choose your stack (node or PHP), database (all SQL vendors), API (REST or GraphQL), and infra (self-hosted or Cloud).
+-   **Pure** — There is no predefined model or proprietary rules for your agnostic schema, and all
+    system settings are stored separately.
+-   **Open** — Our entire codebase is public and transparent, allowing for end-to-end audits.
+    Nothing is obfuscated or black-boxed.
+-   **Portable** — Data is stored in your bespoke database and can be migrated/exported/backed-up at
+    any time. Absolutely no vendor lock-in.
+-   **Limitless** — Create unlimited users, roles, languages, collections, and items. No arbitrary
+    restrictions or paywall limitations.
+-   **Extensible** — Every aspect of the platform is modular, allowing you to adapt, customize, and
+    infinitely extend the Core engine.
+-   **Unopinionated** — Choose your stack (node or PHP), database (all SQL vendors), API (REST or
+    GraphQL), and infra (self-hosted or Cloud).
 
 ## The Directus Ecosystem
 
 ### Open-Source Engine
 
-Completely free and open-source on the GPLv3 license, Directus is publically available within our [npm package](https://www.npmjs.com/package/directus) and main [GitHub repository](https://github.com/directus/directus). It includes our dynamic API engine (node.js), the intuitive Admin App (vue.js 3), this documentation (markdown), and all dependencies.
+Completely free and open-source on the GPLv3 license, Directus is publically available within our
+[npm package](https://www.npmjs.com/package/directus) and main
+[GitHub repository](https://github.com/directus/directus). It includes our dynamic API engine
+(node.js), the intuitive Admin App (vue.js 3), this documentation (markdown), and all dependencies.
 
 ### On-Demand Cloud
 
-Our self-service platform for quick and affordable instances of Directus on a multitenant infrastructure.
+Our self-service platform for quick and affordable instances of Directus on a multitenant
+infrastructure.
 
 ### Enterprise Cloud
 
-Dedicated hardware, custom limits, full white-labeling, uptime SLAs, and more are available on this premium managed solution.
+Dedicated hardware, custom limits, full white-labeling, uptime SLAs, and more are available on this
+premium managed solution.
 
 ### Documentation
 
-[Our online documentation](https://docs.directus.io) describes the most version of our platform. They are written in publicly managed markdown files so the community can help keep them clean and up-to-date!
+[Our online documentation](https://docs.directus.io) describes the most version of our platform.
+They are written in publicly managed markdown files so the community can help keep them clean and
+up-to-date!
 
-* Getting Started: Novice Oriented. For a platform intro and installation.
-* Concepts: Learning Oriented. For understanding the platfom.
-* Guides: Problem Oriented. Follow along with steps while working.
-* Reference: Information Oriented. Look up info and specs while working.
+-   Getting Started: Novice Oriented. For a platform intro and installation.
+-   Concepts: Learning Oriented. For understanding the platfom.
+-   Guides: Problem Oriented. Follow along with steps while working.
+-   Reference: Information Oriented. Look up info and specs while working.
 
-::: tip Versioned Docs
-Docs for specific versions of Directus 9+ are available within the individual Project's App Documentation module.
-:::
+::: tip Versioned Docs Docs for specific versions of Directus 9+ are available within the individual
+Project's App Documentation module. :::
 
 <!-- ### Online Demo
 
@@ -64,20 +89,27 @@ The [Status Page](https://status.directus.io) provides up-to-date information on
 
 ### Marketing Website
 
-Our [marketing site](https://directus.io) provides general information, resources, and team info for the project.
+Our [marketing site](https://directus.io) provides general information, resources, and team info for
+the project.
 
 ### Social
 
-For the latest product info and sneak-peeks into upcoming releases, be sure to follow us on [Twitter](https://twitter.com/directus).
+For the latest product info and sneak-peeks into upcoming releases, be sure to follow us on
+[Twitter](https://twitter.com/directus).
 
 ### Community
 
-Join our growing community of 2,600+ developers on [Discord](https://directus.chat). From community support to seeing where the platform is heading next, it's a great way to get more involved.
+Join our growing community of 2,600+ developers on [Discord](https://directus.chat). From community
+support to seeing where the platform is heading next, it's a great way to get more involved.
 
 ### Languages
 
-In addition to managing multilingual content, the Directus Admin App itself can also be translated into different languages. Our languages are managed through the [Directus CrowdIn](https://locales.directus.io/), which provides a friendly interface and automatically submits pull-requests to the git repository.
+In addition to managing multilingual content, the Directus Admin App itself can also be translated
+into different languages. Our languages are managed through the
+[Directus CrowdIn](https://locales.directus.io/), which provides a friendly interface and
+automatically submits pull-requests to the git repository.
 
 ### Marketplace
 
-Coming soon. A library of free and paid Directus extensions created by our core team and community members.
+Coming soon. A library of free and paid Directus extensions created by our core team and community
+members.
diff --git a/docs/getting-started/quickstart.md b/docs/getting-started/quickstart.md
index 9f43f5c2bb..cbb41fbedf 100644
--- a/docs/getting-started/quickstart.md
+++ b/docs/getting-started/quickstart.md
@@ -1,6 +1,7 @@
 # Quickstart
 
-> If you're looking for the fastest way to get up-and-running with Directus, this guide will walk you through getting things installed, configured, and modeled.
+> If you're looking for the fastest way to get up-and-running with Directus, this guide will walk
+> you through getting things installed, configured, and modeled.
 
 @TODO — Create embedded video overview
 
diff --git a/docs/getting-started/support.md b/docs/getting-started/support.md
index 62a385239f..5c40569607 100644
--- a/docs/getting-started/support.md
+++ b/docs/getting-started/support.md
@@ -1,51 +1,78 @@
 # Technical Support
 
-> Directus is offered completely free and open-source for anyone wishing to self-host the platform. There are many resources, both free and paid, to help you get up-and-running smoothly.
+> Directus is offered completely free and open-source for anyone wishing to self-host the platform.
+> There are many resources, both free and paid, to help you get up-and-running smoothly.
 
 ## Community Support
 
-[Github Discussions](https://github.com/directus/directus/discussions) is great first place to reach out for help. Our community and core developers often check this platform and answer posts. It has the added benefit of being an archival resource for others developers with similar questions.
+[Github Discussions](https://github.com/directus/directus/discussions) is great first place to reach
+out for help. Our community and core developers often check this platform and answer posts. It has
+the added benefit of being an archival resource for others developers with similar questions.
 
-Our [Discord](https://directus.chat) community is another great way to get assisstance. Please keep all questions on the `#help` channel, be considerate, and remember that you are getting free help for a free product.
+Our [Discord](https://directus.chat) community is another great way to get assisstance. Please keep
+all questions on the `#help` channel, be considerate, and remember that you are getting free help
+for a free product.
 
 ## Premium Support
 
-Premium support is included with our Enterprise Cloud service. On-Demand Cloud customers and On-Premise users interested in learning more about our monthly retainer agreements should contact us at [support@directus.io](mailto:support@directus.io).
+Premium support is included with our Enterprise Cloud service. On-Demand Cloud customers and
+On-Premise users interested in learning more about our monthly retainer agreements should contact us
+at [support@directus.io](mailto:support@directus.io).
 
 ## Sponsored Work
 
 ### Commissioned Features
 
-If you need a specific feature added to Directus faster than the normal development timeline, [reach out to us](https://directus.io/contact/) for a quote. Our parent agency will often help subsidize the cost of developing new features if they pass our [80/20 Rule](/getting-started/contributing) and can be merged into the core codebase. Other custom/proprietary development will be built bespoke within our robust extension system.
+If you need a specific feature added to Directus faster than the normal development timeline,
+[reach out to us](https://directus.io/contact/) for a quote. Our parent agency will often help
+subsidize the cost of developing new features if they pass our
+[80/20 Rule](/getting-started/contributing) and can be merged into the core codebase. Other
+custom/proprietary development will be built bespoke within our robust extension system.
 
 ### Expedited Fixes
 
-We triage all reported bugs based on priority and how long the fix is estimated to take. If you need a specific issue resolved sooner, [reach out to us](#) for a quote.
+We triage all reported bugs based on priority and how long the fix is estimated to take. If you need
+a specific issue resolved sooner, [reach out to us](#) for a quote.
 
 ## Frequently Asked Questions
 
 ### Does Directus handle deploying or migrating projects?
 
-Directus includes [export](#) and [backup](#) tools to assist in deploying data changes between environments (eg: from _development_ to _production_), however there is no formal migration workflow.
+Directus includes [export](#) and [backup](#) tools to assist in deploying data changes between
+environments (eg: from _development_ to _production_), however there is no formal migration
+workflow.
 
-Additionally, since Directus stores all of your data in pure SQL, you can use almost any preexisting workflow or toolkit for this process.
+Additionally, since Directus stores all of your data in pure SQL, you can use almost any preexisting
+workflow or toolkit for this process.
 
 ### Does Directus support Mongo/NoSQL?
 
-Not currently. Directus has been built specifically for wrapping _relational_ databases. While we could force Mongo to use tables, columns, and rows via Mongoose object modeling, that approach to non-structured doesn't make a lot of sense. We realize many users are interested in this feature, and will continue to explore its possibility.
+Not currently. Directus has been built specifically for wrapping _relational_ databases. While we
+could force Mongo to use tables, columns, and rows via Mongoose object modeling, that approach to
+non-structured doesn't make a lot of sense. We realize many users are interested in this feature,
+and will continue to explore its possibility.
 
 ### Why haven't you added this feature, or fixed that issue yet?
 
-Directus is primarily a free and open-source project, maintained by a small core team and community contributors who donate their time and resources.
+Directus is primarily a free and open-source project, maintained by a small core team and community
+contributors who donate their time and resources.
 
-Our platform is feature-rich, however we strictly adhere to our [80/20 Rule](/getting-started/contributing) to avoid a messy/bloated codebase. Directus is also quite stable, however new issues still arise, some of which may be triaged with a lower prioritization.
+Our platform is feature-rich, however we strictly adhere to our
+[80/20 Rule](/getting-started/contributing) to avoid a messy/bloated codebase. Directus is also
+quite stable, however new issues still arise, some of which may be triaged with a lower
+prioritization.
 
-If you require more expeditious updates, you can contact us regarding [sponsoring expedited fixes](#) or [commissioning new features](#). You can also [submit a pull request](#) — after all, it is open-source!
+If you require more expeditious updates, you can contact us regarding
+[sponsoring expedited fixes](#) or [commissioning new features](#). You can also
+[submit a pull request](#) — after all, it is open-source!
 
 ### Can you give an ETA for this feature/fix?
 
-If it is [sponsored work](#), then yes, delivery dates are part of our statement of work agreements. Otherwise, most likely not. This is open-source software, work is prioritized internally, and all timelines are subject to change.
+If it is [sponsored work](#), then yes, delivery dates are part of our statement of work agreements.
+Otherwise, most likely not. This is open-source software, work is prioritized internally, and all
+timelines are subject to change.
 
 ### But this is an emergency, my very important project requires it now!
 
-We understand, and are here to help. If you need something prioritized, you can reach out to us to discuss [premium support](#), [sponsoring expedited fixes](#) or [commissioning new features](#).
+We understand, and are here to help. If you need something prioritized, you can reach out to us to
+discuss [premium support](#), [sponsoring expedited fixes](#) or [commissioning new features](#).
diff --git a/docs/guides/collections.md b/docs/guides/collections.md
index 5e8dc304cb..cb800826ce 100644
--- a/docs/guides/collections.md
+++ b/docs/guides/collections.md
@@ -1,77 +1,91 @@
 # Collections
 
-> You can manage your collections within the Data Model section of the App's Settings, via the [API Collections Endpoint](#), or directly within the database. If you're unfamiliar with Directus Collections, please start by reading our [Understanding Collections](#) docs.
+> You can manage your collections within the Data Model section of the App's Settings, via the
+> [API Collections Endpoint](#), or directly within the database. If you're unfamiliar with Directus
+> Collections, please start by reading our [Understanding Collections](#) docs.
 
 ## Creating a Collection
 
 1. Navigate to **Settings > Data Model**
 2. Click the **Create Collection** action button in the header
-3. Enter a unique **Collection Name**, keeping in mind that this is entered as a _key_ that determines the database table name, and is then presented in the App using the [Title Formatter](#).
+3. Enter a unique **Collection Name**, keeping in mind that this is entered as a _key_ that
+   determines the database table name, and is then presented in the App using the
+   [Title Formatter](#).
 4. Optional: Configure the collection's **Primary Key** name and type.
-    * Auto-Incremented Integer
-    * Generated UUID
-    * Manually Entered String
-4. Optional: Enable and rename any desired **System Fields**.
-    * Status
-    * Sort
-    * Created On
-    * Created By
-    * Updated On
-    * Updated By
-5. Click the **Finish Setup** button
+    - Auto-Incremented Integer
+    - Generated UUID
+    - Manually Entered String
+5. Optional: Enable and rename any desired **System Fields**.
+    - Status
+    - Sort
+    - Created On
+    - Created By
+    - Updated On
+    - Updated By
+6. Click the **Finish Setup** button
 
-:::danger Immutable Keys
- The collection name, primary key name/type, and system field names can not be modified after the collection is created.
-:::
+:::danger Immutable Keys The collection name, primary key name/type, and system field names can not
+be modified after the collection is created. :::
 
-::: Database Tables
-Keep in mind that Directus Collections are just a database tables. Therefore you can import or create a table directly in the database, and it will automatically appear within Directus. The first time you manage that table, a `directus_collections` record will be created with default values.
-:::
+::: Database Tables Keep in mind that Directus Collections are just a database tables. Therefore you
+can import or create a table directly in the database, and it will automatically appear within
+Directus. The first time you manage that table, a `directus_collections` record will be created with
+default values. :::
 
 ## Configuring a Collection
 
 ### Fields & Layout
 
-* [Creating a Field](#)
-* [Updating a Field](#)
-* [Deleting a Field](#)
-* [Duplicating a Field](#)
-* [Changing Field Order & Layout](#)
+-   [Creating a Field](#)
+-   [Updating a Field](#)
+-   [Deleting a Field](#)
+-   [Duplicating a Field](#)
+-   [Changing Field Order & Layout](#)
 
 ### Collection Setup
 
-* **Collection Name** — This is the key for the collection. It can not be modified, but you can override it with Translations (see below)
-* **Icon** — The icon used throughout the App when referencing this collection
-* **Note** — A helpful note that explains the collection's purpose
-* **Display Template** — A [Field Template](#) used to create dynamic titles for the collection's items
-* **Hidden** — Toggles if the collection should be globally hidden. Keep in mind that Admin roles can always see all collections.
-* **Singleton** — Is this collection will only contain a single item (eg: an "About Us" form). When enabled, the [Collection Detail](#) will be bypassed, and users are taken directly to the [Item Detail](#) page.
-* **Translation** — Allows translating the collection name into different languages. These [Schema Translations](#) are important for multilingual projects. You can also "translate" a collection name into the default language — helpful for renaming technical table names.
+-   **Collection Name** — This is the key for the collection. It can not be modified, but you can
+    override it with Translations (see below)
+-   **Icon** — The icon used throughout the App when referencing this collection
+-   **Note** — A helpful note that explains the collection's purpose
+-   **Display Template** — A [Field Template](#) used to create dynamic titles for the collection's
+    items
+-   **Hidden** — Toggles if the collection should be globally hidden. Keep in mind that Admin roles
+    can always see all collections.
+-   **Singleton** — Is this collection will only contain a single item (eg: an "About Us" form).
+    When enabled, the [Collection Detail](#) will be bypassed, and users are taken directly to the
+    [Item Detail](#) page.
+-   **Translation** — Allows translating the collection name into different languages. These
+    [Schema Translations](#) are important for multilingual projects. You can also "translate" a
+    collection name into the default language — helpful for renaming technical table names.
 
 ### Archive
 
-The archive feature allows you to enable the collection with a custom soft-delete option. Soft-delete allows users to remove items from the App, but maintains the actual database record for easy recovery.
+The archive feature allows you to enable the collection with a custom soft-delete option.
+Soft-delete allows users to remove items from the App, but maintains the actual database record for
+easy recovery.
 
-* **Archive Field** — The field that holds the archive value
-* **Archive App Filter** — Allows users to view archived items
-* **Archive Value** — The value saved in the Archive Field when archived
-* **Unarchive Value** — The value saved in the Archive Field when unarchived
+-   **Archive Field** — The field that holds the archive value
+-   **Archive App Filter** — Allows users to view archived items
+-   **Archive Value** — The value saved in the Archive Field when archived
+-   **Unarchive Value** — The value saved in the Archive Field when unarchived
 
-:::warning API Responses
-Items that have been archived are still returned normally via the API. It is up to you to filter them out as needed.
-:::
+:::warning API Responses Items that have been archived are still returned normally via the API. It
+is up to you to filter them out as needed. :::
 
-::: Status Field
-When creating a new Collection, you have the option of creating an optional "Status" field. If you choose to include this field, the collection's archive settings will automatically be configured for you.
-:::
+::: Status Field When creating a new Collection, you have the option of creating an optional
+"Status" field. If you choose to include this field, the collection's archive settings will
+automatically be configured for you. :::
 
 ### Sort
 
-The sort feature enables manual drag-and-drop item reordering within the Directus App. This is typically shown on the [Collection Detail](#) page/modal, and can also be used for sorting items within a [Junction Table](#).
+The sort feature enables manual drag-and-drop item reordering within the Directus App. This is
+typically shown on the [Collection Detail](#) page/modal, and can also be used for sorting items
+within a [Junction Table](#).
 
-::: Sort Field
-When creating a new Collection, you have the option of creating an optional "Sort" field. If you choose to include this field, the collection's sort settings will automatically be configured for you.
-:::
+::: Sort Field When creating a new Collection, you have the option of creating an optional "Sort"
+field. If you choose to include this field, the collection's sort settings will automatically be
+configured for you. :::
 
 ## Deleting a Collection
 
@@ -79,6 +93,5 @@ When creating a new Collection, you have the option of creating an optional "Sor
 2. Click the red **Delete Collection** action button in the header
 3. Confirm this decision by clicking **Delete** in the dialog
 
-:::danger Irreversible Change
-This action is permanent and can not be undone. Please proceed with caution.
-:::
+:::danger Irreversible Change This action is permanent and can not be undone. Please proceed with
+caution. :::
diff --git a/docs/guides/extensions/api-endpoints.md b/docs/guides/extensions/api-endpoints.md
index f215cbdbcf..5767a9228f 100644
--- a/docs/guides/extensions/api-endpoints.md
+++ b/docs/guides/extensions/api-endpoints.md
@@ -4,14 +4,18 @@
 
 ## 1. Setup the Boilerplate
 
-Custom endpoints are dynamically loaded from within your project's `/extensions/endpoints` folder. Keep in mind that the extensions directory is configurable within your env file, and may be located elsewhere.
+Custom endpoints are dynamically loaded from within your project's `/extensions/endpoints` folder.
+Keep in mind that the extensions directory is configurable within your env file, and may be located
+elsewhere.
 
-Each endpoint is registered using a registration function within a scoped directory. For example, to create a custom `/custom/my-endpoint/` endpoint, you would add the following function to `/extensions/endpoints/my-endpoint/index.js`.
+Each endpoint is registered using a registration function within a scoped directory. For example, to
+create a custom `/custom/my-endpoint/` endpoint, you would add the following function to
+`/extensions/endpoints/my-endpoint/index.js`.
 
 ```js
 module.exports = function registerEndpoint(router) {
 	router.get('/', (req, res) => res.send('Hello, World!'));
-}
+};
 ```
 
 You can also create several scoped endpoints within a single function:
@@ -22,19 +26,21 @@ You can also create several scoped endpoints within a single function:
 // /custom/my-endpoint/goodbye
 module.exports = function registerEndpoint(router) {
 	router.get('/', (req, res) => res.send('Hello, World!')),
-	router.get('/intro', (req, res) => res.send('Nice to meet you.')),
-	router.get('/goodbye', (req, res) => res.send('Goodbye!'));
-}
+		router.get('/intro', (req, res) => res.send('Nice to meet you.')),
+		router.get('/goodbye', (req, res) => res.send('Goodbye!'));
+};
 ```
 
 ## 2. Develop your Custom Endpoint
 
-The `registerEndpoint` function receives two parameters: `router` and `context`. Router is an express Router instance that is scoped to `/custom/<extension-name>`, while `context` holds the following properties:
+The `registerEndpoint` function receives two parameters: `router` and `context`. Router is an
+express Router instance that is scoped to `/custom/<extension-name>`, while `context` holds the
+following properties:
 
-* `services` — All API interal services.
-* `exceptions` — API exception objects that can be used to throw "proper" errors.
-* `database` — Knex instance that is connected to the current database.
-* `env` — Parsed environment variables.
+-   `services` — All API interal services.
+-   `exceptions` — API exception objects that can be used to throw "proper" errors.
+-   `database` — Knex instance that is connected to the current database.
+-   `env` — Parsed environment variables.
 
 ## 3. Restart the API
 
@@ -60,8 +66,10 @@ module.exports = function registerEndpoint(router, { services, exceptions }) {
 	router.get('/', (req, res) => {
 		recipeService
 			.readByQuery({ sort: 'name', fields: '*' })
-			.then(results => res.json(results))
-			.catch(error => { throw new ServiceUnavailableException(error.message) });
+			.then((results) => res.json(results))
+			.catch((error) => {
+				throw new ServiceUnavailableException(error.message);
+			});
 	});
-}
+};
 ```
diff --git a/docs/guides/extensions/api-hooks.md b/docs/guides/extensions/api-hooks.md
index 4c425a7abf..340038d865 100644
--- a/docs/guides/extensions/api-hooks.md
+++ b/docs/guides/extensions/api-hooks.md
@@ -4,21 +4,26 @@
 
 ## 1. Create a Hook File
 
-Custom hooks are dynamically loaded from within your extensions folder. By default this directory is located at `/extensions`, but it can be configured within your project's env file to be located anywhere. Hooks can be added [standalone](#) or via an [extension bundle](#).
+Custom hooks are dynamically loaded from within your extensions folder. By default this directory is
+located at `/extensions`, but it can be configured within your project's env file to be located
+anywhere. Hooks can be added [standalone](#) or via an [extension bundle](#).
 
 ### Default Standalone Hook Location
+
 ```
 /extensions/hooks/<hook-id>/index.js
 ```
 
 ### Default Bundled Hook Location
+
 ```
 /extensions/bundles/<bundle-id>/hooks/<hook-id>/index.js
 ```
 
 ## 2. Define the Event
 
-Next, you will want to define your event. You can trigger your custom hook with any of the platform's many API events. System events are referenced with the format:
+Next, you will want to define your event. You can trigger your custom hook with any of the
+platform's many API events. System events are referenced with the format:
 
 ```
 <scope>.<action>(.<before>)
@@ -30,45 +35,49 @@ Next, you will want to define your event. You can trigger your custom hook with
 
 ### Scope
 
-The scope determines the API endpoint that is triggered. The `*` wildcard can also be used to include all scopes.
+The scope determines the API endpoint that is triggered. The `*` wildcard can also be used to
+include all scopes.
 
-::: System Scope
-Currently all system tables are available as event scopes except for `directus_migrations` and `directus_sessions`, which don't have relevant endpoints or services.
-:::
+::: System Scope Currently all system tables are available as event scopes except for
+`directus_migrations` and `directus_sessions`, which don't have relevant endpoints or services. :::
 
 ### Action
 
-Defines the triggering operation within the specified context (see chart below). The `*` wildcard can also be used to include all actions available to the scope.
+Defines the triggering operation within the specified context (see chart below). The `*` wildcard
+can also be used to include all actions available to the scope.
 
 ### Before
 
-Many scopes (see chart below) support an optional `.before` suffix for running a _blocking_ hook prior to the event being fired. This allows you to check and/or modify the event's payload before it is processed.
+Many scopes (see chart below) support an optional `.before` suffix for running a _blocking_ hook
+prior to the event being fired. This allows you to check and/or modify the event's payload before it
+is processed.
 
-* `items.create` (Non Blocking)
-* `items.create.before` (Blocking)
+-   `items.create` (Non Blocking)
+-   `items.create.before` (Blocking)
 
-This also allows you to cancel an event based on the logic within the hook. Below is an example of how you can cancel a create event by throwing a standard Directus exception.
+This also allows you to cancel an event based on the logic within the hook. Below is an example of
+how you can cancel a create event by throwing a standard Directus exception.
 
 ```js
 module.exports = function registerHook({ exceptions }) {
-    const { InvalidPayloadException } = exceptions;
+	const { InvalidPayloadException } = exceptions;
 
-    return {
-        'items.create.before': async function(input) {
-            if (LOGIC_TO_CANCEL_EVENT) {
-                throw new InvalidPayloadException(WHAT_IS_WRONG);
-            }
+	return {
+		'items.create.before': async function (input) {
+			if (LOGIC_TO_CANCEL_EVENT) {
+				throw new InvalidPayloadException(WHAT_IS_WRONG);
+			}
 
-            return input;
-        }
-    }
-}
+			return input;
+		},
+	};
+};
 ```
 
 ### Event Format Options
 
 | Scope         | Actions                            | Before   |
-|---------------|------------------------------------|----------|
+| ------------- | ---------------------------------- | -------- |
 | `items`       | `create`, `update` and `delete`    | Optional |
 | `activity`    | `create`, `update` and `delete`    | Optional |
 | `collections` | `create`, `update` and `delete`    | Optional |
@@ -97,36 +106,38 @@ Each custom hook is registered to its event scope using a function with the foll
 ```js
 module.exports = function registerHook() {
 	return {
-		'items.create': function() {
+		'items.create': function () {
 			axios.post('http://example.com/webhook');
-		}
-	}
-}
+		},
+	};
+};
 ```
 
 ## 4. Develop your Custom Hook
 
 ### Register Function
 
-The register function (eg: `module.exports = function registerHook()`) must return an object where the key is the event, and the value is the handler function itself.
+The register function (eg: `module.exports = function registerHook()`) must return an object where
+the key is the event, and the value is the handler function itself.
 
 The `registerHook` function receives a context parameter with the following properties:
 
-* `services` — All API interal services
-* `exceptions` — API exception objects that can be used for throwing "proper" errors
-* `database` — Knex instance that is connected to the current database
-* `env` — Parsed environment variables
+-   `services` — All API interal services
+-   `exceptions` — API exception objects that can be used for throwing "proper" errors
+-   `database` — Knex instance that is connected to the current database
+-   `env` — Parsed environment variables
 
 ### Event Handler Function
 
-The event handler function (eg: `'items.create': function()`) recieves a context parameter with the following properties:
+The event handler function (eg: `'items.create': function()`) recieves a context parameter with the
+following properties:
 
-* `event` — Full event string
-* `accountability` — Information about the current user
-* `collection` — Collection that is being modified
-* `item` — Primary key(s) of the item(s) being modified
-* `action` — Action that is performed
-* `payload` — Payload of the request
+-   `event` — Full event string
+-   `accountability` — Information about the current user
+-   `collection` — Collection that is being modified
+-   `item` — Primary key(s) of the item(s) being modified
+-   `action` — Action that is performed
+-   `payload` — Payload of the request
 
 ## 5. Restart the API
 
@@ -148,11 +159,11 @@ module.exports = function registerHook({ services, exceptions }) {
 
 	return {
 		// Force everything to be admin-only at all times
-		'items.*': async function({ item, accountability }) {
+		'items.*': async function ({ item, accountability }) {
 			if (accountability.admin !== true) throw new ForbiddenException();
 		},
 		// Sync with external recipes service, cancel creation on failure
-		'items.create.before': async function(input, { collection }) {
+		'items.create.before': async function (input, { collection }) {
 			if (collection !== 'recipes') return input;
 
 			try {
@@ -164,7 +175,7 @@ module.exports = function registerHook({ services, exceptions }) {
 			input[0].syncedWithExample = true;
 
 			return input;
-		}
-	}
-}
+		},
+	};
+};
 ```
diff --git a/docs/guides/extensions/displays.md b/docs/guides/extensions/displays.md
index 8c12e07704..6d2f3e984c 100644
--- a/docs/guides/extensions/displays.md
+++ b/docs/guides/extensions/displays.md
@@ -4,7 +4,8 @@
 
 ## 1. Setup the Boilerplate
 
-Every display is a standalone "package" that contains at least a metadata file and a Vue component. We recommend using the following file structure:
+Every display is a standalone "package" that contains at least a metadata file and a Vue component.
+We recommend using the following file structure:
 
 ```
 src/
@@ -18,62 +19,64 @@ src/
 import DisplayComponent from './display.vue';
 
 export default {
-    id: 'custom',
-    name: 'Custom',
-    description: 'This is my custom display!',
-    icon: 'box',
-    handler: DisplayComponent,
-    types: ['string'],
-}
+	id: 'custom',
+	name: 'Custom',
+	description: 'This is my custom display!',
+	icon: 'box',
+	handler: DisplayComponent,
+	types: ['string'],
+};
 ```
 
-* `id` — The unique key for this display. It is good practice to scope proprietary displays with an author prefix.
-* `name` — The human-readable name for this display.
-* `description` — A short description (<80 characters) of this display shown in the App.
-* `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
-* `handler` — A function, or reference to your Vue component.
-* `types` — A CSV of supported [types](#).
+-   `id` — The unique key for this display. It is good practice to scope proprietary displays with
+    an author prefix.
+-   `name` — The human-readable name for this display.
+-   `description` — A short description (<80 characters) of this display shown in the App.
+-   `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
+-   `handler` — A function, or reference to your Vue component.
+-   `types` — A CSV of supported [types](#).
 
-:::
-See [the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/displays/types.ts#L24-L34) for more info on what can go into this object.
-:::
+::: See
+[the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/displays/types.ts#L24-L34)
+for more info on what can go into this object. :::
 
 ### src/display.vue
 
 ```vue
 <template>
-    <div>My Custom Display</div>
+	<div>My Custom Display</div>
 </template>
 
 <script>
-export default {}
+export default {};
 </script>
 ```
 
 The props you can use in an display are:
 
-* `value` — The value of the parent field.
-* `interface` - The interface of the parent field.
-* `interface-options` - The options for the parent field's interface.
-* `type` — The type of the parent field.
-* `collection` — The collection name of the parent field.
-* `field` — The key of the parent field.
+-   `value` — The value of the parent field.
+-   `interface` - The interface of the parent field.
+-   `interface-options` - The options for the parent field's interface.
+-   `type` — The type of the parent field.
+-   `collection` — The collection name of the parent field.
+-   `field` — The key of the parent field.
 
 ---
 
-Alternatively, you can specify a function for the handler. This allows you to make simple displays that don't need a full component rendered:
+Alternatively, you can specify a function for the handler. This allows you to make simple displays
+that don't need a full component rendered:
 
 ```js
 export default {
-    id: 'custom',
-    name: 'Custom',
-    description: 'This is my custom display!',
-    icon: 'box',
-    handler: function(value) {
+	id: 'custom',
+	name: 'Custom',
+	description: 'This is my custom display!',
+	icon: 'box',
+	handler: function (value) {
 		return value.toLowerCase();
 	},
-    types: ['string'],
-}
+	types: ['string'],
+};
 ```
 
 ## 2. Install Dependencies and Configure the Buildchain
@@ -84,7 +87,9 @@ Set up a package.json file by running:
 npm init -y
 ```
 
-To be read by the Admin App, your custom display's Vue component must first be bundled into a single `index.js` file. We recommend bundling your code using Rollup. To install this and the other development dependencies, run this command:
+To be read by the Admin App, your custom display's Vue component must first be bundled into a single
+`index.js` file. We recommend bundling your code using Rollup. To install this and the other
+development dependencies, run this command:
 
 ```bash
 npm i -D rollup rollup-plugin-commonjs rollup-plugin-node-resolve rollup-plugin-terser rollup-plugin-vue@5.0.0 @vue/compiler-sfc vue-template-compiler
@@ -95,27 +100,23 @@ You can then use the following Rollup configuration within `rollup.config.js`:
 ```js
 import { terser } from 'rollup-plugin-terser';
 import resolve from 'rollup-plugin-node-resolve';
-import commonjs from 'rollup-plugin-commonjs'
-import vue from 'rollup-plugin-vue'
+import commonjs from 'rollup-plugin-commonjs';
+import vue from 'rollup-plugin-vue';
 
 export default {
-    input: 'src/index.js',
-    output: {
-        format: 'es',
-        file: 'dist/index.js'
-    },
-    plugins: [
-        terser(),
-        resolve(),
-        commonjs(),
-        vue(),
-    ]
-}
+	input: 'src/index.js',
+	output: {
+		format: 'es',
+		file: 'dist/index.js',
+	},
+	plugins: [terser(), resolve(), commonjs(), vue()],
+};
 ```
 
 ## 3. Develop Your Custom Display
 
-The display itself is simply a function or a Vue component, providing a blank canvas for creating anything you need.
+The display itself is simply a function or a Vue component, providing a blank canvas for creating
+anything you need.
 
 ## 4. Build and Deploy
 
@@ -125,4 +126,6 @@ To build the display for use within Directus, run:
 npx rollup -c
 ```
 
-Finally, move the output from your display's `dist` folder into your project's `/extensions/displays` folder. Keep in mind that the extensions directory is configurable within your env file, and may be located elsewhere.
+Finally, move the output from your display's `dist` folder into your project's
+`/extensions/displays` folder. Keep in mind that the extensions directory is configurable within
+your env file, and may be located elsewhere.
diff --git a/docs/guides/extensions/email-templates.md b/docs/guides/extensions/email-templates.md
index 85384e0e54..b0f2762b24 100644
--- a/docs/guides/extensions/email-templates.md
+++ b/docs/guides/extensions/email-templates.md
@@ -1,6 +1,7 @@
 # Creating a Custom Email Template
 
-> Custom email templates give you control over the presentation of transactional emails sent from the API.
+> Custom email templates give you control over the presentation of transactional emails sent from
+> the API.
 
 ## 1. Setup the Boilerplate
 
diff --git a/docs/guides/extensions/interfaces.md b/docs/guides/extensions/interfaces.md
index 9b5c5599c7..52ea872d4c 100644
--- a/docs/guides/extensions/interfaces.md
+++ b/docs/guides/extensions/interfaces.md
@@ -1,10 +1,12 @@
 # Create a Custom Interface
 
-> Custom interfaces allow you to create new ways of viewing or interacting with data on the Item Detail page.
+> Custom interfaces allow you to create new ways of viewing or interacting with data on the Item
+> Detail page.
 
 ## 1. Setup the Boilerplate
 
-Every interface is a standalone "package" that contains at least a metadata file and a Vue component. We recommend using the following file structure:
+Every interface is a standalone "package" that contains at least a metadata file and a Vue
+component. We recommend using the following file structure:
 
 ```
 src/
@@ -18,46 +20,48 @@ src/
 import InterfaceComponent from './interface.vue';
 
 export default {
-    id: 'custom',
-    name: 'Custom',
-    description: 'This is my custom interface!',
-    icon: 'box',
-    component: InterfaceComponent,
-    types: ['string'],
-}
+	id: 'custom',
+	name: 'Custom',
+	description: 'This is my custom interface!',
+	icon: 'box',
+	component: InterfaceComponent,
+	types: ['string'],
+};
 ```
 
-* `id` — The unique key for this interface. It is good practice to scope proprietary interfaces with an author prefix.
-* `name` — The human-readable name for this interface.
-* `description` — A short description (<80 characters) of this interface shown in the App.
-* `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
-* `component` — A reference to your Vue component.
-* `types` — A CSV of supported [types](#).
+-   `id` — The unique key for this interface. It is good practice to scope proprietary interfaces
+    with an author prefix.
+-   `name` — The human-readable name for this interface.
+-   `description` — A short description (<80 characters) of this interface shown in the App.
+-   `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
+-   `component` — A reference to your Vue component.
+-   `types` — A CSV of supported [types](#).
 
-:::
-See [the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/interfaces/types.ts#L5-L18) for more info on what can go into this object.
-:::
+::: See
+[the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/interfaces/types.ts#L5-L18)
+for more info on what can go into this object. :::
 
 ### src/interface.vue
 
 ```vue
 <template>
-    <div>My Custom Interface</div>
+	<div>My Custom Interface</div>
 </template>
 
 <script>
-export default {}
+export default {};
 </script>
 ```
 
 #### Available Props
 
-* `value` — The value of the parent field.
-* `width` — The layout width of the parent field. Either `half`, `half-left`, `half-right`, `full`, or `fill`.
-* `type` — The type of the parent field.
-* `collection` — The collection name of the parent field.
-* `field` — The key of the parent field.
-* `primary-key` — The current item's primary key.
+-   `value` — The value of the parent field.
+-   `width` — The layout width of the parent field. Either `half`, `half-left`, `half-right`,
+    `full`, or `fill`.
+-   `type` — The type of the parent field.
+-   `collection` — The collection name of the parent field.
+-   `field` — The key of the parent field.
+-   `primary-key` — The current item's primary key.
 
 ## 2. Install Dependencies and Configure the Buildchain
 
@@ -67,7 +71,9 @@ Set up a package.json file by running:
 npm init -y
 ```
 
-To be read by the Admin App, your custom interface's Vue component must first be bundled into a single `index.js` file. We recommend bundling your code using Rollup. To install this and the other development dependencies, run this command:
+To be read by the Admin App, your custom interface's Vue component must first be bundled into a
+single `index.js` file. We recommend bundling your code using Rollup. To install this and the other
+development dependencies, run this command:
 
 ```bash
 npm i -D rollup rollup-plugin-commonjs rollup-plugin-node-resolve rollup-plugin-terser rollup-plugin-vue@5.0.0 @vue/compiler-sfc vue-template-compiler
@@ -78,27 +84,23 @@ You can then use the following Rollup configuration within `rollup.config.js`:
 ```js
 import { terser } from 'rollup-plugin-terser';
 import resolve from 'rollup-plugin-node-resolve';
-import commonjs from 'rollup-plugin-commonjs'
-import vue from 'rollup-plugin-vue'
+import commonjs from 'rollup-plugin-commonjs';
+import vue from 'rollup-plugin-vue';
 
 export default {
-    input: 'src/index.js',
-    output: {
-        format: 'es',
-        file: 'dist/index.js'
-    },
-    plugins: [
-        terser(),
-        resolve(),
-        commonjs(),
-        vue(),
-    ]
-}
+	input: 'src/index.js',
+	output: {
+		format: 'es',
+		file: 'dist/index.js',
+	},
+	plugins: [terser(), resolve(), commonjs(), vue()],
+};
 ```
 
 ## 3. Develop your Custom Interface
 
-The interface itself is simply a Vue component, which provides an blank canvas for creating anything you need.
+The interface itself is simply a Vue component, which provides an blank canvas for creating anything
+you need.
 
 ## 4. Build and Deploy
 
@@ -108,4 +110,6 @@ To build the interface for use within Directus, run:
 npx rollup -c
 ```
 
-Finally, move the output from your interface's `dist` folder into your project's `/extensions/interfaces` folder. Keep in mind that the extensions directory is configurable within your env file, and may be located elsewhere.
+Finally, move the output from your interface's `dist` folder into your project's
+`/extensions/interfaces` folder. Keep in mind that the extensions directory is configurable within
+your env file, and may be located elsewhere.
diff --git a/docs/guides/extensions/layouts.md b/docs/guides/extensions/layouts.md
index 7011b5a534..12eb4e441a 100644
--- a/docs/guides/extensions/layouts.md
+++ b/docs/guides/extensions/layouts.md
@@ -1,10 +1,12 @@
 # Create a Custom Layout
 
-> Custom layouts allow you to create new ways of browsing or viewing data on the Collection Detail page.
+> Custom layouts allow you to create new ways of browsing or viewing data on the Collection Detail
+> page.
 
 ## 1. Setup the Boilerplate
 
-Every layout is a standalone "package" that contains at least a metadata file and a Vue component. We recommend using the following file structure:
+Every layout is a standalone "package" that contains at least a metadata file and a Vue component.
+We recommend using the following file structure:
 
 ```
 src/
@@ -18,40 +20,41 @@ src/
 import LayoutComponent from './layout.vue';
 
 export default {
-    id: 'custom',
-    name: 'Custom',
-	component: LayoutComponent
-}
+	id: 'custom',
+	name: 'Custom',
+	component: LayoutComponent,
+};
 ```
 
-* `id` — The unique key for this layout. It is good practice to scope proprietary layouts with an author prefix.
-* `name` — The human-readable name for this layout.
-* `component` — A reference to your Vue component.
+-   `id` — The unique key for this layout. It is good practice to scope proprietary layouts with an
+    author prefix.
+-   `name` — The human-readable name for this layout.
+-   `component` — A reference to your Vue component.
 
-:::
-See [the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/layouts/types.ts#L4-L9) for more info on what can go into this object.
-:::
+::: See
+[the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/layouts/types.ts#L4-L9)
+for more info on what can go into this object. :::
 
 ### src/layout.vue
 
 ```vue
 <template>
-    <div>My Custom Layout</div>
+	<div>My Custom Layout</div>
 </template>
 
 <script>
-export default {}
+export default {};
 </script>
 ```
 
 The props you can use in an layout are:
 
-* `collection` — The current collection's name.
-* `selection` (sync) - Any currently selected items.
-* `layout-options` (sync) - The user's current saved layout options.
-* `layout-query` (sync) - The user's layout query parameters. (eg: sort, limit, etc)
-* `filters` (sync) - The user's currently active filters.
-* `search-query` (sync) - The user's current search query.
+-   `collection` — The current collection's name.
+-   `selection` (sync) - Any currently selected items.
+-   `layout-options` (sync) - The user's current saved layout options.
+-   `layout-query` (sync) - The user's layout query parameters. (eg: sort, limit, etc)
+-   `filters` (sync) - The user's currently active filters.
+-   `search-query` (sync) - The user's current search query.
 
 ## 2. Install Dependencies and Configure the Buildchain
 
@@ -61,7 +64,9 @@ Set up a package.json file by running:
 npm init -y
 ```
 
-To be read by the Admin App, your custom layouts's Vue component must first be bundled into a single `index.js` file. We recommend bundling your code using Rollup. To install this and the other development dependencies, run this command:
+To be read by the Admin App, your custom layouts's Vue component must first be bundled into a single
+`index.js` file. We recommend bundling your code using Rollup. To install this and the other
+development dependencies, run this command:
 
 ```bash
 npm i -D rollup rollup-plugin-commonjs rollup-plugin-node-resolve rollup-plugin-terser rollup-plugin-vue@5.0.0 @vue/compiler-sfc vue-template-compiler
@@ -72,27 +77,23 @@ You can then use the following Rollup configuration within `rollup.config.js`:
 ```js
 import { terser } from 'rollup-plugin-terser';
 import resolve from 'rollup-plugin-node-resolve';
-import commonjs from 'rollup-plugin-commonjs'
-import vue from 'rollup-plugin-vue'
+import commonjs from 'rollup-plugin-commonjs';
+import vue from 'rollup-plugin-vue';
 
 export default {
-    input: 'src/index.js',
-    output: {
-        format: 'es',
-        file: 'dist/index.js'
-    },
-    plugins: [
-        terser(),
-        resolve(),
-        commonjs(),
-        vue(),
-    ]
-}
+	input: 'src/index.js',
+	output: {
+		format: 'es',
+		file: 'dist/index.js',
+	},
+	plugins: [terser(), resolve(), commonjs(), vue()],
+};
 ```
 
 ## 3. Develop Your Custom Layout
 
-The layout itself is simply a Vue component, which provides an blank canvas for creating anything you need.
+The layout itself is simply a Vue component, which provides an blank canvas for creating anything
+you need.
 
 ## 4. Build and Deploy
 
@@ -102,4 +103,6 @@ To build the layout for use within Directus, run:
 npx rollup -c
 ```
 
-Finally, move the output from your layout's `dist` folder into your project's `/extensions/layouts` folder. Keep in mind that the extensions directory is configurable within your env file, and may be located elsewhere.
+Finally, move the output from your layout's `dist` folder into your project's `/extensions/layouts`
+folder. Keep in mind that the extensions directory is configurable within your env file, and may be
+located elsewhere.
diff --git a/docs/guides/extensions/modules.md b/docs/guides/extensions/modules.md
index ea6bf52664..a549ee7090 100644
--- a/docs/guides/extensions/modules.md
+++ b/docs/guides/extensions/modules.md
@@ -4,7 +4,8 @@
 
 ## 1. Setup the Boilerplate
 
-Every module is a standalone "package" that contains at least a metadata file and a Vue component. We recommend using the following file structure:
+Every module is a standalone "package" that contains at least a metadata file and a Vue component.
+We recommend using the following file structure:
 
 ```
 src/
@@ -18,36 +19,37 @@ src/
 import ModuleComponent from './module.vue';
 
 export default {
-    id: 'custom',
-    name: 'Custom',
+	id: 'custom',
+	name: 'Custom',
 	icon: 'box',
 	routes: [
 		{
 			path: '/',
-			component: ModuleComponent
-		}
-	]
-}
+			component: ModuleComponent,
+		},
+	],
+};
 ```
 
-* `id` — The unique key for this module. It is good practice to scope proprietary interfaces with an author prefix.
-* `name` — The human-readable name for this module.
-* `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
-* `routes` — Details the routes in your module per the Vue router.
+-   `id` — The unique key for this module. It is good practice to scope proprietary interfaces with
+    an author prefix.
+-   `name` — The human-readable name for this module.
+-   `icon` — An icon name from the material icon set, or the extended list of Directus custom icons.
+-   `routes` — Details the routes in your module per the Vue router.
 
-:::
-See [the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/modules/types.ts#L6-L17) for more info on what can go into this object.
-:::
+::: See
+[the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/modules/types.ts#L6-L17)
+for more info on what can go into this object. :::
 
 ### src/module.vue
 
 ```vue
 <template>
-    <div>My Custom Module</div>
+	<div>My Custom Module</div>
 </template>
 
 <script>
-export default {}
+export default {};
 </script>
 ```
 
@@ -63,7 +65,9 @@ Set up a package.json file by running:
 npm init -y
 ```
 
-To be read by the Admin App, your custom module's Vue component must first be bundled into a single `index.js` file. We recommend bundling your code using Rollup. To install this and the other development dependencies, run this command:
+To be read by the Admin App, your custom module's Vue component must first be bundled into a single
+`index.js` file. We recommend bundling your code using Rollup. To install this and the other
+development dependencies, run this command:
 
 ```bash
 npm i -D rollup rollup-plugin-commonjs rollup-plugin-node-resolve rollup-plugin-terser rollup-plugin-vue@5.0.0 @vue/compiler-sfc vue-template-compiler
@@ -74,27 +78,23 @@ You can then use the following Rollup configuration within `rollup.config.js`:
 ```js
 import { terser } from 'rollup-plugin-terser';
 import resolve from 'rollup-plugin-node-resolve';
-import commonjs from 'rollup-plugin-commonjs'
-import vue from 'rollup-plugin-vue'
+import commonjs from 'rollup-plugin-commonjs';
+import vue from 'rollup-plugin-vue';
 
 export default {
-    input: 'src/index.js',
-    output: {
-        format: 'es',
-        file: 'dist/index.js'
-    },
-    plugins: [
-        terser(),
-        resolve(),
-        commonjs(),
-        vue(),
-    ]
-}
+	input: 'src/index.js',
+	output: {
+		format: 'es',
+		file: 'dist/index.js',
+	},
+	plugins: [terser(), resolve(), commonjs(), vue()],
+};
 ```
 
 ## 3. Develop Your Custom Module
 
-The module itself is simply a Vue component, which provides an blank canvas for creating anything you need.
+The module itself is simply a Vue component, which provides an blank canvas for creating anything
+you need.
 
 ## 4. Build and Deploy
 
@@ -104,4 +104,6 @@ To build the module for use within Directus, run:
 npx rollup -c
 ```
 
-Finally, move the output from your module's `dist` folder into your project's `/extensions/modules` folder. Keep in mind that the extensions directory is configurable within your env file, and may be located elsewhere.
+Finally, move the output from your module's `dist` folder into your project's `/extensions/modules`
+folder. Keep in mind that the extensions directory is configurable within your env file, and may be
+located elsewhere.
diff --git a/docs/guides/field-types/many-to-any-field.md b/docs/guides/field-types/many-to-any-field.md
index 11fe0fb34f..9d4a09ce39 100644
--- a/docs/guides/field-types/many-to-any-field.md
+++ b/docs/guides/field-types/many-to-any-field.md
@@ -1,3 +1,3 @@
 # Creating a Many-to-Any Field
 
-> TK
\ No newline at end of file
+> TK
diff --git a/docs/guides/field-types/translated-fields.md b/docs/guides/field-types/translated-fields.md
index 0c45efc937..2ee1332bab 100644
--- a/docs/guides/field-types/translated-fields.md
+++ b/docs/guides/field-types/translated-fields.md
@@ -1,3 +1,3 @@
 # Creating Translated Fields
 
-> TK
\ No newline at end of file
+> TK
diff --git a/docs/guides/fields.md b/docs/guides/fields.md
index 2ab388dd94..ccfb9b60a5 100644
--- a/docs/guides/fields.md
+++ b/docs/guides/fields.md
@@ -1,6 +1,8 @@
 # Fields
 
-> You can manage your fields within the Data Model section of the App's Settings, via the [API Fields Endpoint](#), or directly within the database. If you're unfamiliar with Directus Fields, please start by reading our [Understanding Fields](#) docs.
+> You can manage your fields within the Data Model section of the App's Settings, via the
+> [API Fields Endpoint](#), or directly within the database. If you're unfamiliar with Directus
+> Fields, please start by reading our [Understanding Fields](#) docs.
 
 ## Creating a Field
 
@@ -16,9 +18,10 @@
 -   [Many-to-Any Field](#)
 -   [Translated Fields](#)
 
-::: tip Database Fields
-Keep in mind that Directus Fields are just a database columns. Therefore you can import or create a column directly in the database, and it will automatically appear within Directus. The first time you manage that column, a `directus_fields` record will be created with default values.
-:::
+::: tip Database Fields Keep in mind that Directus Fields are just a database columns. Therefore you
+can import or create a column directly in the database, and it will automatically appear within
+Directus. The first time you manage that column, a `directus_fields` record will be created with
+default values. :::
 
 ## Duplicating a Field
 
@@ -26,9 +29,8 @@ Keep in mind that Directus Fields are just a database columns. Therefore you can
 2. Click the **More Options** icon for the field you want to delete
 3. Click the **Duplicate Field** option
 
-:::warning Relational and Primary Key Fields
-It is not currently possible to duplicate relational fields or a collection's primary key.
-:::
+:::warning Relational and Primary Key Fields It is not currently possible to duplicate relational
+fields or a collection's primary key. :::
 
 ## Adjusting Field Layout
 
@@ -54,6 +56,5 @@ The layout of the collection's form is determined by the following field options
 3. Click the **Delete Field** option
 4. Confirm this decision by clicking **Delete** in the dialog
 
-::: danger Irreversible Change
-This action is permanent and can not be undone. Please proceed with caution.
-:::
+::: danger Irreversible Change This action is permanent and can not be undone. Please proceed with
+caution. :::
diff --git a/docs/guides/files.md b/docs/guides/files.md
index 911b736cb1..bd9a504948 100644
--- a/docs/guides/files.md
+++ b/docs/guides/files.md
@@ -1,6 +1,7 @@
 # Files & Thumbnails
 
-> Directus offers a full-featured Digital Asset Management (DAM) system, multiple storage adapters, private file permissions, and on-demand image thumbnail generation.
+> Directus offers a full-featured Digital Asset Management (DAM) system, multiple storage adapters,
+> private file permissions, and on-demand image thumbnail generation.
 
 ## Uploading a File
 
@@ -8,19 +9,20 @@
 
 ## Accessing an Original File
 
-The location of your actual file originals is based on the project's configuration, but you can consistently access them via the API using the following URL.
+The location of your actual file originals is based on the project's configuration, but you can
+consistently access them via the API using the following URL.
 
 ```
 example.com/assets/<file-id>
 example.com/assets/1ac73658-8b62-4dea-b6da-529fbc9d01a4
 ```
 
-![Original File](../assets/original.jpg)
-_Original File Used Below — 602KB and 1800x1200_
+![Original File](../assets/original.jpg) _Original File Used Below — 602KB and 1800x1200_
 
-::: warning Direct File Access
-While you may _technically_ be able to access your original files within their actual filesystem directory (eg: `/uploads/<filename_disk>` for the default local storage configuration), it is recommended that you always use the Directus API. This is the only way that you can take advantage of file permissions and other built-in features.
-:::
+::: warning Direct File Access While you may _technically_ be able to access your original files
+within their actual filesystem directory (eg: `/uploads/<filename_disk>` for the default local
+storage configuration), it is recommended that you always use the Directus API. This is the only way
+that you can take advantage of file permissions and other built-in features. :::
 
 ## Creating Thumbnail Presets
 
@@ -31,23 +33,28 @@ While you may _technically_ be able to access your original files within their a
 5. Enter the **Fit**, **Width**, **Height**, and **Quality** for the preset
 6. Click the **Save** action button in the header
 
-::: tip Storage Asset Transform
-The **Storage Asset Transform** can be used in conjunction with the presets to force an allow-list or completely disable the thumbnailing system. The options for this are:
+::: tip Storage Asset Transform The **Storage Asset Transform** can be used in conjunction with the
+presets to force an allow-list or completely disable the thumbnailing system. The options for this
+are:
 
 -   **All** — Any valid thumbnail request will be returned
 -   **None** — No thumbnails will be returned, not even presets
--   **Presets Only** — Only valid Storage Asset Presets will be returned
-    :::
+-   **Presets Only** — Only valid Storage Asset Presets will be returned :::
 
 ## Requesting a Thumbnail
 
-Fetching thumbnails is as easy as adding query parameters to the original file's URL. If a requested thumbnail doesn't yet exist, it is dynamically generated and immediately returned. When requesting a thumbnail, the following parameters are all required.
+Fetching thumbnails is as easy as adding query parameters to the original file's URL. If a requested
+thumbnail doesn't yet exist, it is dynamically generated and immediately returned. When requesting a
+thumbnail, the following parameters are all required.
 
--   **`fit`** — The **fit** of the thumbnail while always preserving the aspect ratio, can be any of the following options:
+-   **`fit`** — The **fit** of the thumbnail while always preserving the aspect ratio, can be any of
+    the following options:
     -   `cover` — Covers both width/height by cropping/clipping to fit
     -   `contain` — Contain within both width/height using "letterboxing" as needed
-    -   `inside` — Resize to be as large as possible, ensuring dimensions are less than or equal to the requested width and height
-    -   `outside` — Resize to be as small as possible, ensuring dimensions are greater than or equal to the requested width and height
+    -   `inside` — Resize to be as large as possible, ensuring dimensions are less than or equal to
+        the requested width and height
+    -   `outside` — Resize to be as small as possible, ensuring dimensions are greater than or equal
+        to the requested width and height
 -   **`width`** — The **width** of the thumbnail in pixels
 -   **`height`** — The **height** of the thumbnail in pixels
 -   **`quality`** — The **quality** of the thumbnail (`0` to `100`)
@@ -61,7 +68,9 @@ example.com/assets/1ac73658-8b62-4dea-b6da-529fbc9d01a4?fit=cover&width=200&heig
 
 Alternatively, you can reference a specific thumbnail by its preset key.
 
--   **`key`** — This **key** of the [Storage Asset Preset](/guides/files#creating-thumbnail-presets), a shortcut for the above parameters
+-   **`key`** — This **key** of the
+    [Storage Asset Preset](/guides/files#creating-thumbnail-presets), a shortcut for the above
+    parameters
 
 ```
 example.com/assets/<file-id>?key=<preset-key>
@@ -70,19 +79,23 @@ example.com/assets/1ac73658-8b62-4dea-b6da-529fbc9d01a4?key=card
 
 ### Cover vs Contain
 
-For easier comparison, both of the examples below were requested at `200` width, `200` height, and `75` quality. The `cover` thumbnail forces the dimensions, trimming the outside edges as needed. The `contain` thumbnail always maintains its aspect ratio, shrinking the image to fit _within_ the dimensions and adding "letterboxing" as needed.
+For easier comparison, both of the examples below were requested at `200` width, `200` height, and
+`75` quality. The `cover` thumbnail forces the dimensions, trimming the outside edges as needed. The
+`contain` thumbnail always maintains its aspect ratio, shrinking the image to fit _within_ the
+dimensions and adding "letterboxing" as needed.
 
 | Cover                                                       | Contain                                                         |
 | ----------------------------------------------------------- | --------------------------------------------------------------- |
 | ![Cover](../assets/200-200-cover-75.jpg)<br>_8KB • 200x200_ | ![Contain](../assets/200-200-contain-75.jpg)<br>_6KB • 200x133_ |
 
-::: Aspect Ratio
-Images are never stretched or distorted even when changing the aspect ratio.
-:::
+::: Aspect Ratio Images are never stretched or distorted even when changing the aspect ratio. :::
 
 ### Quality vs Filesize
 
-The quality parameter can be any integer from `0-100`. Qualities closer to `0` have lower filesizes, but also poor image quality due to compression artifacts. Values closer to `100` have larger filesizes, but better image quality. Below are four possible qualities (200x200 cover) to visually compare the balance between compression and filesize.
+The quality parameter can be any integer from `0-100`. Qualities closer to `0` have lower filesizes,
+but also poor image quality due to compression artifacts. Values closer to `100` have larger
+filesizes, but better image quality. Below are four possible qualities (200x200 cover) to visually
+compare the balance between compression and filesize.
 
 | 25%                                             | 50%                                             | 75%                                             | 100%                                               |
 | ----------------------------------------------- | ----------------------------------------------- | ----------------------------------------------- | -------------------------------------------------- |
diff --git a/docs/guides/installation/cli.md b/docs/guides/installation/cli.md
index e9d5e35a40..c60ab49ef2 100644
--- a/docs/guides/installation/cli.md
+++ b/docs/guides/installation/cli.md
@@ -2,11 +2,15 @@
 
 ## 1. Confirm Minimum Requirements are Met
 
-**The only requirements for Directus is an actively maintained version of [Node.js](https://nodejs.org/en/about/releases/).** Currently that is v10+, however in April 2021, node v10 will leave _Maintenance Long-Term Support (LTS)_ status, and node v12+ will become the new minimum requirement.
+**The only requirements for Directus is an actively maintained version of
+[Node.js](https://nodejs.org/en/about/releases/).** Currently that is v10+, however in April 2021,
+node v10 will leave _Maintenance Long-Term Support (LTS)_ status, and node v12+ will become the new
+minimum requirement.
 
 ### Databases
 
-Directus currently supports the following databases, with our minimum version being based on each vendor's official support/LTS.
+Directus currently supports the following databases, with our minimum version being based on each
+vendor's official support/LTS.
 
 | Database      | Version |
 | ------------- | ------- |
@@ -17,9 +21,8 @@ Directus currently supports the following databases, with our minimum version be
 | OracleDB      | TBD     |
 | MariaDB       | 10.1+   |
 
-::: Variants
-In addition to the databases above, other variants are also supported, including **AWS Aurora** (MySQL), and **AWS Redshift** (PostgreSQL).
-:::
+::: Variants In addition to the databases above, other variants are also supported, including **AWS
+Aurora** (MySQL), and **AWS Redshift** (PostgreSQL). :::
 
 ## 2. Create a Project
 
@@ -29,9 +32,8 @@ Create a new Directus project by running the following npm command.
 npx create-directus-project my-project
 ```
 
-:::warning
-Except for SQLite, the database must already be running before creating your Directus project.
-:::
+:::warning Except for SQLite, the database must already be running before creating your Directus
+project. :::
 
 ## 3. Start your Project
 
diff --git a/docs/guides/installation/digitalocean-one-click.md b/docs/guides/installation/digitalocean-one-click.md
index ead2852e0e..de7f792560 100644
--- a/docs/guides/installation/digitalocean-one-click.md
+++ b/docs/guides/installation/digitalocean-one-click.md
@@ -2,16 +2,17 @@
 
 ## 1. Create a DigitalOcean Account
 
-If you don't already have an account you'll need to create one, you can use [our referral link](https://m.do.co/c/389c62a20bb5) to get $100 of free credit!
+If you don't already have an account you'll need to create one, you can use
+[our referral link](https://m.do.co/c/389c62a20bb5) to get \$100 of free credit!
 
 ## 2. Create a Project
 
-Navigate to the [Directus One-Click App](https://marketplace.digitalocean.com/apps/directus) within the DigitalOcean Marketplace and follow these steps:
+Navigate to the [Directus One-Click App](https://marketplace.digitalocean.com/apps/directus) within
+the DigitalOcean Marketplace and follow these steps:
 
-* Click "Create Directus Droplet"
-* Configure your VPS (any plan/size)
-* Choose a hostname (anything you want)
-* Click "Create Droplet"
+-   Click "Create Directus Droplet"
+-   Configure your VPS (any plan/size)
+-   Choose a hostname (anything you want)
+-   Click "Create Droplet"
 
 ## 3. TK
-
diff --git a/docs/guides/installation/docker.md b/docs/guides/installation/docker.md
index 82e91a45c1..0b3ade5300 100644
--- a/docs/guides/installation/docker.md
+++ b/docs/guides/installation/docker.md
@@ -17,9 +17,11 @@ docker run -p 8055:8055 directus/directus:v9.1.2
 ```bash
 docker run -e ENV_VAR=VALUE -p 8055:8055 directus/directus
 ```
+
 ## Create admin user using docker
- 
-To create an admin user using specific credentials using docker set the following environment variables:
+
+To create an admin user using specific credentials using docker set the following environment
+variables:
 
 ```bash
 DIRECTUS_ADMIN_EMAIL="admin@example.com"
diff --git a/docs/guides/installation/heroku.md b/docs/guides/installation/heroku.md
index b7707df1dd..70f707780a 100644
--- a/docs/guides/installation/heroku.md
+++ b/docs/guides/installation/heroku.md
@@ -1,3 +1,3 @@
 # Installing with Heroku
 
-## 1. TK
\ No newline at end of file
+## 1. TK
diff --git a/docs/guides/installation/manual.md b/docs/guides/installation/manual.md
index 3ee94fd2a2..e133a2c906 100644
--- a/docs/guides/installation/manual.md
+++ b/docs/guides/installation/manual.md
@@ -28,4 +28,5 @@ At this point you have the option of installing other dependencies, such as Redi
 
 ## 5. Setup a Configuration File
 
-Finally, you'll need to setup your `.env` file, or configure the environment variables through other means, such as Docker, etc.
+Finally, you'll need to setup your `.env` file, or configure the environment variables through other
+means, such as Docker, etc.
diff --git a/docs/guides/presets.md b/docs/guides/presets.md
index 00f5fc921e..2aba33bbd1 100644
--- a/docs/guides/presets.md
+++ b/docs/guides/presets.md
@@ -1,6 +1,8 @@
 # Collection Presets
 
-> Presets store the exact state of a [collection detail](#) page. These can be used to set layout defaults for a user, or to define bookmarks that can be used to recall windows into specific datasets.
+> Presets store the exact state of a [collection detail](#) page. These can be used to set layout
+> defaults for a user, or to define bookmarks that can be used to recall windows into specific
+> datasets.
 
 ## Creating a Preset
 
@@ -8,26 +10,31 @@
 2. Click the **Create Preset** action button in the header
 3. Complete the **other preset form fields** outlined below
 
-* **Collection** — The collection of this preset; supports any project collection, Directus Files, or Directus Users
-* **Scope** — The users that will have access to this preset, either Global, a specific Role, or an individual User
-* **Layout** — The collection detail's layout this preset applies to
-* **Name** — If left blank, this preset will act as a Default for the collection/layout; if given a name, it will be shown as a bookmark
+-   **Collection** — The collection of this preset; supports any project collection, Directus Files,
+    or Directus Users
+-   **Scope** — The users that will have access to this preset, either Global, a specific Role, or
+    an individual User
+-   **Layout** — The collection detail's layout this preset applies to
+-   **Name** — If left blank, this preset will act as a Default for the collection/layout; if given
+    a name, it will be shown as a bookmark
 
-After you have completed the form, the layout preview will be populated with live data. You can now tailor the layout as desired by updating the preview or the filter component in the page sidebar.
+After you have completed the form, the layout preview will be populated with live data. You can now
+tailor the layout as desired by updating the preview or the filter component in the page sidebar.
 
-Each preset saves all of the information needed to recreate a view of the collection/layou, including: the full-text search query, any advanced filters added, sort field, sort direction, and all other specific layout options.
+Each preset saves all of the information needed to recreate a view of the collection/layou,
+including: the full-text search query, any advanced filters added, sort field, sort direction, and
+all other specific layout options.
 
-::: Defaults vs Bookmarks
-It's important to be aware of the difference between a collection's _defaults_ and its _bookmarks_, both of which are configured by presets. A _default_ is how a user will initially view the collection detail without any further customization, while a _bookmark_ is a named dataset that can be recalled at any point via the [collection navigation](#).
-:::
+::: Defaults vs Bookmarks It's important to be aware of the difference between a collection's
+_defaults_ and its _bookmarks_, both of which are configured by presets. A _default_ is how a user
+will initially view the collection detail without any further customization, while a _bookmark_ is a
+named dataset that can be recalled at any point via the [collection navigation](#). :::
 
-::: System Defaults
-You can also adjust the defaults and bookmarks for the Directus Activity, Directus Files, and Directus Users collections.
-:::
+::: System Defaults You can also adjust the defaults and bookmarks for the Directus Activity,
+Directus Files, and Directus Users collections. :::
 
-::: Order of Defaults
-Multiple defaults can be configured for a user, either for different layouts of even the same layout. In this case, the preset priority is: User, then Role, then Global.
-:::
+::: Order of Defaults Multiple defaults can be configured for a user, either for different layouts
+of even the same layout. In this case, the preset priority is: User, then Role, then Global. :::
 
 ## Deleting a Preset
 
@@ -35,6 +42,5 @@ Multiple defaults can be configured for a user, either for different layouts of
 2. Click the red **Delete Preset** action button in the header
 3. Confirm this decision by clicking **Delete** in the dialog
 
-:::danger Irreversible Change
-This action is permanent and can not be undone. Please proceed with caution.
-:::
+:::danger Irreversible Change This action is permanent and can not be undone. Please proceed with
+caution. :::
diff --git a/docs/guides/projects.md b/docs/guides/projects.md
index 9e86ca8401..562df6d84b 100644
--- a/docs/guides/projects.md
+++ b/docs/guides/projects.md
@@ -1,35 +1,37 @@
 # Projects
 
-> Every installation of Directus creates a single project. If you're unfamiliar with Directus Projects, please start by reading our [Platform Overview](#).
+> Every installation of Directus creates a single project. If you're unfamiliar with Directus
+> Projects, please start by reading our [Platform Overview](#).
 
 ## Creating a Project
 
 To install Directus, choose one of the following methods.
 
-* [Command Line Interface (CLI)](/guides/installation/cli.md)
-* [Docker](/guides/installation/docker.md)
-* [Manually](/guides/installation/manual.md)
+-   [Command Line Interface (CLI)](/guides/installation/cli.md)
+-   [Docker](/guides/installation/docker.md)
+-   [Manually](/guides/installation/manual.md)
 
 ### Deployment Guides
 
-* [Amazon AWS](#)
-* [DigitalOcean Droplet](#)
-* [DigitalOcean One-Click](/guides/installation/digitalocean-one-click.md)
-* [Google App Engine](#)
-* [Heroku](/guides/installation/heroku.md)
-* [Microsoft Azure](#)
+-   [Amazon AWS](#)
+-   [DigitalOcean Droplet](#)
+-   [DigitalOcean One-Click](/guides/installation/digitalocean-one-click.md)
+-   [Google App Engine](#)
+-   [Heroku](/guides/installation/heroku.md)
+-   [Microsoft Azure](#)
 
 ## Configuring a Project
 
-All project configuration is handled by the `.env` file within the `/api` directory. This file accepts a number of environment variables, each is explained in the following reference:
+All project configuration is handled by the `.env` file within the `/api` directory. This file
+accepts a number of environment variables, each is explained in the following reference:
 
-* [Environment Variables](#)
+-   [Environment Variables](#)
 
 ## Upgrading a Project
 
 1. Backup your project
 2. Run `npm update`
-<!-- 3. Run `directus migrate:latest` to update the DB ——— @TODO finalize when CLI is finalized -->
+ <!-- 3. Run `directus migrate:latest` to update the DB ——— @TODO finalize when CLI is finalized -->
 
 ## Backing-up a Project
 
@@ -45,6 +47,6 @@ All project configuration is handled by the `.env` file within the `/api` direct
 4. **Delete the project's root directory** from the server
 5. **Delete all Directus system tables** (`directus_*`) from the database
 
-::: Pure SQL
-After completing this process, you will be left with a pure SQL database, with no trace that Directus was ever installed. Any external services connecting to your database's project tables directly (eg: SQL queries) should continue working normally.
-:::
+::: Pure SQL After completing this process, you will be left with a pure SQL database, with no trace
+that Directus was ever installed. Any external services connecting to your database's project tables
+directly (eg: SQL queries) should continue working normally. :::
diff --git a/docs/guides/roles-and-permissions.md b/docs/guides/roles-and-permissions.md
index 625e0fd603..ef298662bb 100644
--- a/docs/guides/roles-and-permissions.md
+++ b/docs/guides/roles-and-permissions.md
@@ -1,6 +1,7 @@
 # Roles & Permissions
 
-> During installation, Directus automatically includes an initial "Admin" role with complete project access. After that, you are free to extend and customize these as much as is needed.
+> During installation, Directus automatically includes an initial "Admin" role with complete project
+> access. After that, you are free to extend and customize these as much as is needed.
 
 ## Creating a Role
 
@@ -12,21 +13,26 @@
 
 ## Configuring a Role
 
-* **Permissions** — Defines the role's access permissions, see [Configuring Role Permissions](#) and [Configuring System Permissions](#)
-* **Role Name** — This is the name of the role
-* **Role Icon** — The icon used throughout the App when referencing this role
-* **Description** — A helpful note that explains the role's purpose
-* **App Access** — Allows logging in to the App
-* **Admin Access** — Gives full permission to project data and Settings
-* **IP Access** — An allow-list of IP addresses from which the platform can be accessed, empty allows all
-* **Require 2FA** — Forces all users within this role to use two-factor authentication
-* **Users in Role** — A list of all users within this role
-* **Module Navigation** — Overrides the visible modules, see [Customizing the Module Navigation](#)
-* **Collection Navigation** — Overrides the collection module's navigation, see [Customizing the Collection Navigation](#)
+-   **Permissions** — Defines the role's access permissions, see [Configuring Role Permissions](#)
+    and [Configuring System Permissions](#)
+-   **Role Name** — This is the name of the role
+-   **Role Icon** — The icon used throughout the App when referencing this role
+-   **Description** — A helpful note that explains the role's purpose
+-   **App Access** — Allows logging in to the App
+-   **Admin Access** — Gives full permission to project data and Settings
+-   **IP Access** — An allow-list of IP addresses from which the platform can be accessed, empty
+    allows all
+-   **Require 2FA** — Forces all users within this role to use two-factor authentication
+-   **Users in Role** — A list of all users within this role
+-   **Module Navigation** — Overrides the visible modules, see
+    [Customizing the Module Navigation](#)
+-   **Collection Navigation** — Overrides the collection module's navigation, see
+    [Customizing the Collection Navigation](#)
 
 ### Customizing the Module Navigation
 
-The options in the [Module Bar](#) can be overridden with custom options per role. When this setting is empty, the default modules are used.
+The options in the [Module Bar](#) can be overridden with custom options per role. When this setting
+is empty, the default modules are used.
 
 1. Navigate to **Settings > Roles & Permissions > [Role Name]**
 2. Scroll to the **Module Navigation** field
@@ -36,7 +42,8 @@ The options in the [Module Bar](#) can be overridden with custom options per rol
 6. Enter a relative (App) or absolute (external) **link** for the module
 7. Use the drag handles to **drag-and-drop** the modules into the desired order
 
-If you are looking to replicate the default modules, paste the following configuration into the Module Navigation field using the [Raw Value](#) field label option.
+If you are looking to replicate the default modules, paste the following configuration into the
+Module Navigation field using the [Raw Value](#) field label option.
 
 ```json
 [
@@ -63,78 +70,93 @@ If you are looking to replicate the default modules, paste the following configu
 ]
 ```
 
-:::warning Settings Module
-The settings module is not controlled by this configuration. It is always added to the end of the list for any user's with Admin Access.
-:::
+:::warning Settings Module The settings module is not controlled by this configuration. It is always
+added to the end of the list for any user's with Admin Access. :::
 
-::: Customizing Existing Modules
-You can enter the link to an existing module to customize its name or icon. For example, you can use `/collections` to override the Collections module.
-:::
+::: Customizing Existing Modules You can enter the link to an existing module to customize its name
+or icon. For example, you can use `/collections` to override the Collections module. :::
 
 ### Customizing the Collection Navigation
 
-The collections in the [Navigation Bar](#) can be overridden with custom options per role. When this setting is empty, all collections that the user has permission to see are shown alphabetically in a single, unlabeled group.
+The collections in the [Navigation Bar](#) can be overridden with custom options per role. When this
+setting is empty, all collections that the user has permission to see are shown alphabetically in a
+single, unlabeled group.
 
 1. Navigate to **Settings > Roles & Permissions > [Role Name]**
 2. Scroll to the **Collection Navigation** field
 3. Click the **Add New Group** button to add a Grouping
 4. Enter a **Group Name**, or leave it empty to simply show a divider
 5. Choose if the group's **Accordion** will be...
-   * Always Open (Default)
-   * Start Open
-   * Start Collapsed
+    - Always Open (Default)
+    - Start Open
+    - Start Collapsed
 6. Click the **Add New Collection** button to add a Collection
 7. Choose a **Collection** from the dropdown
 8. Use the drag handles to **drag-and-drop** the groups/collections into the desired order
 
 ## Configuring Role Permissions
 
-Directus possesses an extremely granular, yet easy to configure, permissions system. When creating a new role, permissions are disabled for all project collections by default — allowing you to give explicit access to only what is required. Individual permissions are applied to the role, and each is scoped to a specific collection and CRUD action (create, read, update, delete).
+Directus possesses an extremely granular, yet easy to configure, permissions system. When creating a
+new role, permissions are disabled for all project collections by default — allowing you to give
+explicit access to only what is required. Individual permissions are applied to the role, and each
+is scoped to a specific collection and CRUD action (create, read, update, delete).
 
-:::warning Saves Automatically
-Every change made to the permissions of a role is saved automatically and instantly.
-:::
+:::warning Saves Automatically Every change made to the permissions of a role is saved automatically
+and instantly. :::
 
-:::warning Admin Roles
-If a role is set to **Admin Access** then it is granted complete access to the platoform, and therefore the permission configuration field is disabled.
-:::
+:::warning Admin Roles If a role is set to **Admin Access** then it is granted complete access to
+the platoform, and therefore the permission configuration field is disabled. :::
 
 1. Navigate to **Settings > Roles & Permissions > [Role Name]**
 2. Scroll to the **Permissions** section
 3. **Click the icon** for the collection (row) and action (column) you want to set
 4. Choose the desired permission level: **All Access**, **No Access**, or **Use Custom**
 
-If you selected _All Access_ or _No Access_ then setup is complete. If you chose to customize the permissions, then a modal will open with additional configuration options. Continue with the appropriate guide below based on the _action_ of the permission.
+If you selected _All Access_ or _No Access_ then setup is complete. If you chose to customize the
+permissions, then a modal will open with additional configuration options. Continue with the
+appropriate guide below based on the _action_ of the permission.
 
 #### Create (Custom)
 
-5. **Field Permissions** control which fields accept a value on create. Fields are individually toggled.
-6. **Field Validation** define the rules for field values on create, as defined by the [Filter Rules](#) entered.
-7. **Field Presets** control the field defaults when creating an item, as defined by the [Item Object](#) entered.
+5. **Field Permissions** control which fields accept a value on create. Fields are individually
+   toggled.
+6. **Field Validation** define the rules for field values on create, as defined by the
+   [Filter Rules](#) entered.
+7. **Field Presets** control the field defaults when creating an item, as defined by the
+   [Item Object](#) entered.
 
 #### Read (Custom)
 
-5. **Item Permissions** control which items can be read, as defined by the [Filter Rules](#) entered.
+5. **Item Permissions** control which items can be read, as defined by the [Filter Rules](#)
+   entered.
 6. **Field Permissions** control which fields can be read. Fields are individually toggled.
 
 #### Update (Custom)
 
-5. **Item Permissions** control which items can be updated, as defined by the [Filter Rules](#) entered.
+5. **Item Permissions** control which items can be updated, as defined by the [Filter Rules](#)
+   entered.
 6. **Field Permissions** control which fields can be updated. Fields are individually toggled.
-7. **Field Validation** define the rules for field values on update, as defined by the [Filter Rules](#) entered.
-8. **Field Presets** control the field defaults when updating an item, as defined by the [Item Object](#) entered.
+7. **Field Validation** define the rules for field values on update, as defined by the
+   [Filter Rules](#) entered.
+8. **Field Presets** control the field defaults when updating an item, as defined by the
+   [Item Object](#) entered.
 
 #### Delete (Custom)
 
-5. **Item Permissions** control which items can be deleted, as defined by the [Filter Rules](#) entered.
+5. **Item Permissions** control which items can be deleted, as defined by the [Filter Rules](#)
+   entered.
 
 ## Configuring System Permissions
 
-In addition to setting permissions for your project's collections, you can also tailor the permissions for system collections. It is important to note that when [App Access](#) is enabled for a role, Directus will automatically add permission for the neccesary system collections. To edit system permissions, simply click the "System Collections" toggle, and then edit permissions using the same steps as with project collections.
+In addition to setting permissions for your project's collections, you can also tailor the
+permissions for system collections. It is important to note that when [App Access](#) is enabled for
+a role, Directus will automatically add permission for the neccesary system collections. To edit
+system permissions, simply click the "System Collections" toggle, and then edit permissions using
+the same steps as with project collections.
 
-::: Resetting System Permissions
-To reset the role's system permissions for proper App access, expand the system collections and then click "Reset System Permissions" at the bottom of the listing.
-:::
+::: Resetting System Permissions To reset the role's system permissions for proper App access,
+expand the system collections and then click "Reset System Permissions" at the bottom of the
+listing. :::
 
 ## Deleting a Role
 
@@ -142,14 +164,12 @@ To reset the role's system permissions for proper App access, expand the system
 2. Click the red **Delete Role** action button in the header
 3. Confirm this decision by clicking **Delete** in the dialog
 
-:::warning Users in a Deleted Role
-If you delete a role that still has users in it, those users will be given a `NULL` role, which denies their App access and limits them to the [Public](#) permissions. They can then be reassigned to a new role by an admin.
-:::
+:::warning Users in a Deleted Role If you delete a role that still has users in it, those users will
+be given a `NULL` role, which denies their App access and limits them to the [Public](#)
+permissions. They can then be reassigned to a new role by an admin. :::
 
-:::warning Last Admin
-You must maintain at least one role/user with Admin Access so that you can still properly manage the project.
-:::
+:::warning Last Admin You must maintain at least one role/user with Admin Access so that you can
+still properly manage the project. :::
 
-:::warning Public Role
-You can not delete the Public role, as it is part of the core platform. To disable it completely, simply turn off all Public access permissions.
-:::
+:::warning Public Role You can not delete the Public role, as it is part of the core platform. To
+disable it completely, simply turn off all Public access permissions. :::
diff --git a/docs/guides/users.md b/docs/guides/users.md
index f0d2f63d35..f60cc9fb3a 100644
--- a/docs/guides/users.md
+++ b/docs/guides/users.md
@@ -1,6 +1,8 @@
 # Users
 
-> You are prompted to enter the details of your first admin user during the installation process. After that, you are free to create as many users as you'd like. There is no limit to the number of users in a project.
+> You are prompted to enter the details of your first admin user during the installation process.
+> After that, you are free to create as many users as you'd like. There is no limit to the number of
+> users in a project.
 
 ## Creating a User
 
@@ -17,7 +19,8 @@
 4. Enter **one or more email addresses**, separated by commas, in the modal
 5. Click **Invite**
 
-At this point the invited user(s) will recieve an email with a link to the App where they set a password and enable their account.
+At this point the invited user(s) will recieve an email with a link to the App where they set a
+password and enable their account.
 
 ## Configuring a User
 
@@ -25,37 +28,33 @@ At this point the invited user(s) will recieve an email with a link to the App w
 2. Click on the user you wish to manage
 3. Complete any of the [User Fields](/concepts/app-overview.md#user-detail)
 
-::: User Preferences
-This section of the User Detail is only visible/editable by the current user, and admins.
-:::
+::: User Preferences This section of the User Detail is only visible/editable by the current user,
+and admins. :::
 
 ### Status
 
-* **Draft** — An incomplete user; no App/API access
-* **Invited** — Has a pending invite to the project; no App/API access until accepted
-* **Active** — The only status that has proper access to the App and API
-* **Suspended** — A user that has been temporarily disabled; no App/API access
-* **Archived** — A soft-deleted user; no App/API access
+-   **Draft** — An incomplete user; no App/API access
+-   **Invited** — Has a pending invite to the project; no App/API access until accepted
+-   **Active** — The only status that has proper access to the App and API
+-   **Suspended** — A user that has been temporarily disabled; no App/API access
+-   **Archived** — A soft-deleted user; no App/API access
 
-:::warning Admin Only
-Only admins can adjust this field's value.
-:::
+:::warning Admin Only Only admins can adjust this field's value. :::
 
 ### Role
 
-Setting the user's role determines their access, permissions, and App presentation. You can adjust a user's role from the User Detail page, or from the _Users in Role_ field within **Settings > Roles & Permissions > [Role Name]**.
+Setting the user's role determines their access, permissions, and App presentation. You can adjust a
+user's role from the User Detail page, or from the _Users in Role_ field within **Settings > Roles &
+Permissions > [Role Name]**.
 
-:::warning Admin Only
-Only admins can adjust this field's value.
-:::
+:::warning Admin Only Only admins can adjust this field's value. :::
 
 ### Token
 
-A user's token is an alternate way to [authenticate into the API](#) using a static string. When NULL, the token is disabled. When enabled, ensure that a secure string is used.
+A user's token is an alternate way to [authenticate into the API](#) using a static string. When
+NULL, the token is disabled. When enabled, ensure that a secure string is used.
 
-:::warning Admin Only
-Only admins can adjust this field's value.
-:::
+:::warning Admin Only Only admins can adjust this field's value. :::
 
 ## Archiving a User
 
@@ -64,9 +63,8 @@ Only admins can adjust this field's value.
 3. Click the orange **Archive User** action button in the header
 4. Confirm this decision by clicking **Archive** in the dialog
 
-:::warning Disables Access
-Archiving uses _soft-delete_, therefore archived users are unable to access the App or API.
-:::
+:::warning Disables Access Archiving uses _soft-delete_, therefore archived users are unable to
+access the App or API. :::
 
 ## Deleting a User
 
@@ -75,6 +73,5 @@ Archiving uses _soft-delete_, therefore archived users are unable to access the
 3. Click the red **Delete User** action button in the header
 4. Confirm this decision by clicking **Delete** in the dialog
 
-:::danger Irreversible Change
-Unlike the soft-delete of archiving, this process is a hard-delete. Therefore, this action is permanent and can not be undone. Please proceed with caution.
-:::
+:::danger Irreversible Change Unlike the soft-delete of archiving, this process is a hard-delete.
+Therefore, this action is permanent and can not be undone. Please proceed with caution. :::
diff --git a/docs/guides/webhooks.md b/docs/guides/webhooks.md
index e9aa1ffc08..bd15d1b234 100644
--- a/docs/guides/webhooks.md
+++ b/docs/guides/webhooks.md
@@ -1,6 +1,8 @@
 # Webhooks
 
-> In addition to writing custom code for more complex [event hooks](#), Directus provides a way to quickly configure webhooks through the App. These send HTTP requests when a specific event is triggered within the project.
+> In addition to writing custom code for more complex [event hooks](#), Directus provides a way to
+> quickly configure webhooks through the App. These send HTTP requests when a specific event is
+> triggered within the project.
 
 ## Creating Webhooks
 
@@ -8,13 +10,14 @@
 2. Click the **Create Webhook** action button in the header
 3. Complete the **other webhook form fields** outlined below
 
-* **Name** — A name to help remember this webhooks purpose
-* **Method** — Send as either a HTTP `GET` or `POST` request
-* **URL** — The URL to send the request to
-* **Status** — Whether the webhook is active (enabled) or inactive (disabled)
-* **Data** — Whether the event's data should be sent along with the request
-* **Trigger Actions** — The specific actions that will trigger the event
-* **Trigger Collections** — The specific collections for which the above actions will trigger the event
+-   **Name** — A name to help remember this webhooks purpose
+-   **Method** — Send as either a HTTP `GET` or `POST` request
+-   **URL** — The URL to send the request to
+-   **Status** — Whether the webhook is active (enabled) or inactive (disabled)
+-   **Data** — Whether the event's data should be sent along with the request
+-   **Trigger Actions** — The specific actions that will trigger the event
+-   **Trigger Collections** — The specific collections for which the above actions will trigger the
+    event
 
 ## Disabling Webhooks
 
@@ -27,6 +30,5 @@
 2. Click the red **Delete Webhook** action button in the header
 3. Confirm this decision by clicking **Delete** in the dialog
 
-:::danger Irreversible Change
-This action is permanent and can not be undone. Please proceed with caution.
-:::
+:::danger Irreversible Change This action is permanent and can not be undone. Please proceed with
+caution. :::
diff --git a/docs/guides/white-labeling.md b/docs/guides/white-labeling.md
index 3297222b28..fdae264e07 100644
--- a/docs/guides/white-labeling.md
+++ b/docs/guides/white-labeling.md
@@ -1,65 +1,85 @@
 # White-Labeling a Project
 
-> The Directus App UX/UI is meant to be _transparent_, and uses "form follows function" as the guiding design principle. This allows the platform to be completely tailored to your branding, end-to-end.
+> The Directus App UX/UI is meant to be _transparent_, and uses "form follows function" as the
+> guiding design principle. This allows the platform to be completely tailored to your branding,
+> end-to-end.
 
 ## Project Settings
 
 1. Navigate to **Settings > Project Settings**
 2. Configure any of the following **branding fields**
 
-* **Project Name** — The name used at the top of the [Navigation Bar](#) and on the login/public pages
-* **Project URL** — The URL when clicking the logo at the top of the [Module Bar](#)
-* **Project Color** — The color used behind the logo at the top of the [Module Bar](#), on the login/public pages, and for the browser's FavIcon
-* **Project Logo** — A 40x40 pixel logo at the top of the [Module Bar](#) and on the login/public pages
+-   **Project Name** — The name used at the top of the [Navigation Bar](#) and on the login/public
+    pages
+-   **Project URL** — The URL when clicking the logo at the top of the [Module Bar](#)
+-   **Project Color** — The color used behind the logo at the top of the [Module Bar](#), on the
+    login/public pages, and for the browser's FavIcon
+-   **Project Logo** — A 40x40 pixel logo at the top of the [Module Bar](#) and on the login/public
+    pages
 
-::: Recommended Logo Styling
-The 40x40 pixel Project Logo is inset within the 64x64 pixel Project Color square. To avoid a "boxy" look, we recommend using a SVG or PNG logo with transparency.
-:::
+::: Recommended Logo Styling The 40x40 pixel Project Logo is inset within the 64x64 pixel Project
+Color square. To avoid a "boxy" look, we recommend using a SVG or PNG logo with transparency. :::
 
-::: Browser FavIcon & Title
-The project color and logo are also used to set the dynamic favicon, and the project title is used in the browser's title. This furthers the bespoke appearance of your platform and makes it easier to differentiate between different Directus projects.
-:::
+::: Browser FavIcon & Title The project color and logo are also used to set the dynamic favicon, and
+the project title is used in the browser's title. This furthers the bespoke appearance of your
+platform and makes it easier to differentiate between different Directus projects. :::
 
 ### Public Page Styling
 
-In addition to the above options, you can also apply the following additional styling to your prject's [public pages](#).
+In addition to the above options, you can also apply the following additional styling to your
+prject's [public pages](#).
 
-* **Public Foreground** — An image shown on the right-side pane of public pages; max 400px width
-* **Public Background** — An image displayed behind the above foreground image, shown full-bleed within the right-side pane of public pages
-* **Public Note** — A helpful note displayed at the bottom of the right-side pane of public pages; supports markdown for rich-text formatting
+-   **Public Foreground** — An image shown on the right-side pane of public pages; max 400px width
+-   **Public Background** — An image displayed behind the above foreground image, shown full-bleed
+    within the right-side pane of public pages
+-   **Public Note** — A helpful note displayed at the bottom of the right-side pane of public pages;
+    supports markdown for rich-text formatting
 
-::: Default Background Color
-When a Public Background image is not set, the right-side pane of public pages uses the Project Color instead.
-:::
+::: Default Background Color When a Public Background image is not set, the right-side pane of
+public pages uses the Project Color instead. :::
 
 ## Themes & Custom CSS
 
-The Directus App has been developed with customization and extensibility in mind. Colors and styles referenced within the codebase all use CSS variables, and therefore it is easy to make comprehensive changes to the App styling.
+The Directus App has been developed with customization and extensibility in mind. Colors and styles
+referenced within the codebase all use CSS variables, and therefore it is easy to make comprehensive
+changes to the App styling.
 
-* **Themes** — See the [Light Theme](https://github.com/directus/directus/blob/main/app/src/styles/themes/_light.scss) or [Dark Theme](https://github.com/directus/directus/blob/main/app/src/styles/themes/_dark.scss)
-* **Typography** — See the [Fonts](https://github.com/directus/directus/blob/main/app/src/styles/_type-styles.scss) and [Type Styles](https://github.com/directus/directus/blob/main/app/src/styles/mixins/type-styles.scss)
-* **Variables** — See the [Global Variables](https://github.com/directus/directus/blob/main/app/src/styles/_variables.scss)
+-   **Themes** — See the
+    [Light Theme](https://github.com/directus/directus/blob/main/app/src/styles/themes/_light.scss)
+    or [Dark Theme](https://github.com/directus/directus/blob/main/app/src/styles/themes/_dark.scss)
+-   **Typography** — See the
+    [Fonts](https://github.com/directus/directus/blob/main/app/src/styles/_type-styles.scss) and
+    [Type Styles](https://github.com/directus/directus/blob/main/app/src/styles/mixins/type-styles.scss)
+-   **Variables** — See the
+    [Global Variables](https://github.com/directus/directus/blob/main/app/src/styles/_variables.scss)
 
-You can override any core CSS, including the above variables, directly within the App through project Settings.
+You can override any core CSS, including the above variables, directly within the App through
+project Settings.
 
 1. Navigate to **Settings > Project Settings**
 2. Scroll to the **CSS Overrides** field
 3. Enter any **valid CSS**
 4. Click the **Save** action button in the header
 
-::: Action Styling
-The `--primary` variable (and its shades) control call-to-actions and all other "Directus blue" elements within the App. While it may be tempting to override this variable with your brand's color, please first review the following warnings:
+::: Action Styling The `--primary` variable (and its shades) control call-to-actions and all other
+"Directus blue" elements within the App. While it may be tempting to override this variable with
+your brand's color, please first review the following warnings:
 
-* Avoid using yellow, orange, or red hues that give a sense of "danger"
-* Avoid low-contrast colors like yellows, grays, etc, that might not be easily visible
-* Avoid low-saturation colors like black, which might not properly highlight CTAs
+-   Avoid using yellow, orange, or red hues that give a sense of "danger"
+-   Avoid low-contrast colors like yellows, grays, etc, that might not be easily visible
+-   Avoid low-saturation colors like black, which might not properly highlight CTAs
 
 :::
 
 ## API Reference
 
-In addition to the static core docs, Directus also includes a [Dynamic API Reference](#) based on your project's schema. This includes tailored endpoint info for each collection within your data model, customizing the documentation to your specific project.
+In addition to the static core docs, Directus also includes a [Dynamic API Reference](#) based on
+your project's schema. This includes tailored endpoint info for each collection within your data
+model, customizing the documentation to your specific project.
 
 ## System Table Prefix
 
-Most white-labeling takes place in the presentation layer of the platform's App, but in some cases even the API and/or database needs to be a bit more agnostic. For that reason, Directus allows changing the prefix used by system tables. By default this is set to use `directus_*` to avoid any potential conflicts, but you can override this within the [Environment Variables](#).
+Most white-labeling takes place in the presentation layer of the platform's App, but in some cases
+even the API and/or database needs to be a bit more agnostic. For that reason, Directus allows
+changing the prefix used by system tables. By default this is set to use `directus_*` to avoid any
+potential conflicts, but you can override this within the [Environment Variables](#).
diff --git a/docs/readme.md b/docs/readme.md
index a0310ed221..b43e4632e0 100644
--- a/docs/readme.md
+++ b/docs/readme.md
@@ -6,43 +6,43 @@ Welcome to the Directus documentation.
 
 Novice Oriented. For a platform intro and installation.
 
-* [Introduction](#)
-* [Support](#)
-* [Contributing](#)
-* [Backing Directus](#)
+-   [Introduction](#)
+-   [Support](#)
+-   [Contributing](#)
+-   [Backing Directus](#)
 
 ## Concepts
 
 Learning Oriented. For understanding the platfom.
 
-* [Platform Overview](#)
-* [App Overview](#)
-* [App Extensions](#)
-* [Activity & Versions](#)
-* [Files & Thumbnails](#)
-* [Internationalization](#)
-* [Relationships](#)
-* [Users, Roles & Permissions](#)
+-   [Platform Overview](#)
+-   [App Overview](#)
+-   [App Extensions](#)
+-   [Activity & Versions](#)
+-   [Files & Thumbnails](#)
+-   [Internationalization](#)
+-   [Relationships](#)
+-   [Users, Roles & Permissions](#)
 
 ## Guides
 
 Problem Oriented. Follow along with steps while working.
 
-* [Collections](#)
-* [Fields](#)
-* [Presets](#)
-* [Projects](#)
-* [Roles & Permissions](#)
-* [Users](#)
-* [Webhooks](#)
-* [White-Labeling](#)
+-   [Collections](#)
+-   [Fields](#)
+-   [Presets](#)
+-   [Projects](#)
+-   [Roles & Permissions](#)
+-   [Users](#)
+-   [Webhooks](#)
+-   [White-Labeling](#)
 
 ## Reference
 
 Information Oriented. Look up info and specs while working.
 
-* [Command Line Interface](#)
-* [Environment Variables](#)
-* [Error Codes](#)
-* [Filter Rules](#)
-* [Item Objects](#)
+-   [Command Line Interface](#)
+-   [Environment Variables](#)
+-   [Error Codes](#)
+-   [Filter Rules](#)
+-   [Item Objects](#)
diff --git a/docs/reference/api/activity.md b/docs/reference/api/activity.md
index a226a749c6..c2babc5ec7 100644
--- a/docs/reference/api/activity.md
+++ b/docs/reference/api/activity.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Activity',
-            'description': 'All events that happen within Directus are tracked and stored in the activities collection. This gives you full accountability over everything that happens.',
+            'description':
+                'All events that happen within Directus are tracked and stored in the activities
+                collection. This gives you full accountability over everything that happens.',
             'x-collection': 'directus_activity',
         },
 }
@@ -12,4 +14,5 @@
 
 # Activity
 
-All events that happen within Directus are tracked and stored in the activities collection. This gives you full accountability over everything that happens.
+All events that happen within Directus are tracked and stored in the activities collection. This
+gives you full accountability over everything that happens.
diff --git a/docs/reference/api/assets.md b/docs/reference/api/assets.md
index b4034697b0..9a08c94ee4 100644
--- a/docs/reference/api/assets.md
+++ b/docs/reference/api/assets.md
@@ -4,7 +4,8 @@
     'tag':
         {
             'name': 'Assets',
-            'description': 'Image typed files can be dynamically resized and transformed to fit any need.',
+            'description':
+                'Image typed files can be dynamically resized and transformed to fit any need.',
         },
 }
 ---
diff --git a/docs/reference/api/authentication.md b/docs/reference/api/authentication.md
index 2ed0a73cba..1fe861eabe 100644
--- a/docs/reference/api/authentication.md
+++ b/docs/reference/api/authentication.md
@@ -4,11 +4,14 @@
     'tag':
         {
             'name': 'Authentication',
-            'description': 'All events that happen within Directus are tracked and stored in the activities collection. This gives you full accountability over everything that happens.',
+            'description':
+                'All events that happen within Directus are tracked and stored in the activities
+                collection. This gives you full accountability over everything that happens.',
         },
 }
 ---
 
 # Authentication
 
-All events that happen within Directus are tracked and stored in the activities collection. This gives you full accountability over everything that happens.
+All events that happen within Directus are tracked and stored in the activities collection. This
+gives you full accountability over everything that happens.
diff --git a/docs/reference/api/collections.md b/docs/reference/api/collections.md
index 76b72f88a7..1f50c9afca 100644
--- a/docs/reference/api/collections.md
+++ b/docs/reference/api/collections.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Collections',
-            'description': 'Collections are the individual collections of items, similar to tables in a database. Changes to collections will alter the schema of the database.',
+            'description':
+                'Collections are the individual collections of items, similar to tables in a
+                database. Changes to collections will alter the schema of the database.',
             'x-collection': 'directus_collections',
         },
 }
@@ -12,4 +14,5 @@
 
 # Collections
 
-Collections are the individual collections of items, similar to tables in a database. Changes to collections will alter the schema of the database.
+Collections are the individual collections of items, similar to tables in a database. Changes to
+collections will alter the schema of the database.
diff --git a/docs/reference/api/extensions.md b/docs/reference/api/extensions.md
index 73cf959063..aed686070d 100644
--- a/docs/reference/api/extensions.md
+++ b/docs/reference/api/extensions.md
@@ -4,11 +4,14 @@
     'tag':
         {
             'name': 'Extensions',
-            'description': 'Directus can easily be extended through the addition of several types of extensions, including layouts, interfaces, and modules.',
+            'description':
+                'Directus can easily be extended through the addition of several types of
+                extensions, including layouts, interfaces, and modules.',
         },
 }
 ---
 
 # Extensions
 
-Directus can easily be extended through the addition of several types of extensions, including layouts, interfaces, and modules.
+Directus can easily be extended through the addition of several types of extensions, including
+layouts, interfaces, and modules.
diff --git a/docs/reference/api/fields.md b/docs/reference/api/fields.md
index 403a867ab3..30b1b290cb 100644
--- a/docs/reference/api/fields.md
+++ b/docs/reference/api/fields.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Fields',
-            'description': 'Fields are individual pieces of content within an item. They are mapped to columns in the database.',
+            'description':
+                'Fields are individual pieces of content within an item. They are mapped to columns
+                in the database.',
             'x-collection': 'directus_fields',
         },
 }
diff --git a/docs/reference/api/files.md b/docs/reference/api/files.md
index 6ddbbacc43..9ca482124d 100644
--- a/docs/reference/api/files.md
+++ b/docs/reference/api/files.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Files',
-            'description': 'Files can be saved in any given location. Directus has a powerful assets endpoint that can be used to generate thumbnails for images on the fly.',
+            'description':
+                'Files can be saved in any given location. Directus has a powerful assets endpoint
+                that can be used to generate thumbnails for images on the fly.',
             'x-collection': 'directus_files',
         },
 }
@@ -12,4 +14,5 @@
 
 # Files
 
-Files can be saved in any given location. Directus has a powerful assets endpoint that can be used to generate thumbnails for images on the fly.
+Files can be saved in any given location. Directus has a powerful assets endpoint that can be used
+to generate thumbnails for images on the fly.
diff --git a/docs/reference/api/introduction.md b/docs/reference/api/introduction.md
index 05a445fcdf..c2b0c84219 100644
--- a/docs/reference/api/introduction.md
+++ b/docs/reference/api/introduction.md
@@ -1,5 +1,8 @@
 # API Reference
 
-Directus offers both a RESTful and GraphQL API to manage the data in the database. The API has predictable resource-oriented URLs, relies on standard HTTP status codes, and uses JSON for input and output.
+Directus offers both a RESTful and GraphQL API to manage the data in the database. The API has
+predictable resource-oriented URLs, relies on standard HTTP status codes, and uses JSON for input
+and output.
 
-The input/output of the API differs greatly for individual installs, as most of the endpoints will return data that's based on your specific schema.
+The input/output of the API differs greatly for individual installs, as most of the endpoints will
+return data that's based on your specific schema.
diff --git a/docs/reference/api/items.md b/docs/reference/api/items.md
index e9d0731382..f1e25c203c 100644
--- a/docs/reference/api/items.md
+++ b/docs/reference/api/items.md
@@ -4,11 +4,14 @@
     'tag':
         {
             'name': 'Items',
-            'description': 'Items are individual pieces of data in your database. They can be anything, from articles, to IoT status checks.',
+            'description':
+                'Items are individual pieces of data in your database. They can be anything, from
+                articles, to IoT status checks.',
         },
 }
 ---
 
 # Items
 
-Items are individual pieces of data in your database. They can be anything, from articles, to IoT status checks.
+Items are individual pieces of data in your database. They can be anything, from articles, to IoT
+status checks.
diff --git a/docs/reference/api/presets.md b/docs/reference/api/presets.md
index 5b98b1ad11..a19ea123b3 100644
--- a/docs/reference/api/presets.md
+++ b/docs/reference/api/presets.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Presets',
-            'description': 'Presets hold the preferences of individual users of the platform. This allows Directus to show and maintain custom item listings for users of the app.',
+            'description':
+                'Presets hold the preferences of individual users of the platform. This allows
+                Directus to show and maintain custom item listings for users of the app.',
             'x-collection': 'directus_presets',
         },
 }
@@ -12,4 +14,5 @@
 
 # Presets
 
-Presets hold the preferences of individual users of the platform. This allows Directus to show and maintain custom item listings for users of the app.
+Presets hold the preferences of individual users of the platform. This allows Directus to show and
+maintain custom item listings for users of the app.
diff --git a/docs/reference/api/relations.md b/docs/reference/api/relations.md
index bdc284b2d1..ae649fbb89 100644
--- a/docs/reference/api/relations.md
+++ b/docs/reference/api/relations.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Relations',
-            'description': 'What data is linked to what other data. Allows you to assign authors to articles, products to sales, and whatever other structures you can think of.',
+            'description':
+                'What data is linked to what other data. Allows you to assign authors to articles,
+                products to sales, and whatever other structures you can think of.',
             'x-collection': 'directus_relations',
         },
 }
@@ -12,4 +14,5 @@
 
 # Relations
 
-What data is linked to what other data. Allows you to assign authors to articles, products to sales, and whatever other structures you can think of.
+What data is linked to what other data. Allows you to assign authors to articles, products to sales,
+and whatever other structures you can think of.
diff --git a/docs/reference/api/revisions.md b/docs/reference/api/revisions.md
index 97380a8ffc..fbb3a79a7c 100644
--- a/docs/reference/api/revisions.md
+++ b/docs/reference/api/revisions.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Revisions',
-            'description': "Revisions are individual changes to items made. Directus keeps track of changes made, so you're able to revert to a previous state at will.",
+            'description':
+                "Revisions are individual changes to items made. Directus keeps track of changes
+                made, so you're able to revert to a previous state at will.",
             'x-collection': 'directus_revisions',
         },
 }
@@ -12,4 +14,5 @@
 
 # Revisions
 
-Revisions are individual changes to items made. Directus keeps track of changes made, so you're able to revert to a previous state at will.
+Revisions are individual changes to items made. Directus keeps track of changes made, so you're able
+to revert to a previous state at will.
diff --git a/docs/reference/api/server.md b/docs/reference/api/server.md
index 6427410be3..2f37347bc7 100644
--- a/docs/reference/api/server.md
+++ b/docs/reference/api/server.md
@@ -4,11 +4,14 @@
     'tag':
         {
             'name': 'Server',
-            'description': "Access to where Directus runs. Allows you to make sure your server has everything needed to run the platform, and check what kind of latency we're dealing with.",
+            'description':
+                "Access to where Directus runs. Allows you to make sure your server has everything
+                needed to run the platform, and check what kind of latency we're dealing with.",
         },
 }
 ---
 
 # Server
 
-Access to where Directus runs. Allows you to make sure your server has everything needed to run the platform, and check what kind of latency we're dealing with.
+Access to where Directus runs. Allows you to make sure your server has everything needed to run the
+platform, and check what kind of latency we're dealing with.
diff --git a/docs/reference/api/utilities.md b/docs/reference/api/utilities.md
index 05f041f8c2..efe7cab9c3 100644
--- a/docs/reference/api/utilities.md
+++ b/docs/reference/api/utilities.md
@@ -4,7 +4,9 @@
     'tag':
         {
             'name': 'Utilities',
-            'description': 'Directus comes with various utility endpoints you can use to simplify your development flow.',
+            'description':
+                'Directus comes with various utility endpoints you can use to simplify your
+                development flow.',
         },
 }
 ---
diff --git a/docs/reference/environment-variables.md b/docs/reference/environment-variables.md
index 16a21eca0b..8c72ac713c 100644
--- a/docs/reference/environment-variables.md
+++ b/docs/reference/environment-variables.md
@@ -1,7 +1,8 @@
 # Environment Variables
 
-> Each Directus project supports a number of environment variables for configuration. These variables are added to the `/api/.env` file, with an example file at `/api/example.env` for easier boilerplate setup.
-
+> Each Directus project supports a number of environment variables for configuration. These
+> variables are added to the `/api/.env` file, with an example file at `/api/example.env` for easier
+> boilerplate setup.
 
 ## General
 
@@ -15,18 +16,20 @@ URL where your API can be reached on the web.<br>**Default: `/`**
 
 ### `LOG_LEVEL`
 
-What level of detail to log. One of `fatal`, `error`, `warn`, `info`, `debug`, `trace` or `silent`.<br>**Default: `info`**
+What level of detail to log. One of `fatal`, `error`, `warn`, `info`, `debug`, `trace` or
+`silent`.<br>**Default: `info`**
 
 ### `LOG_STYLE`
 
 Render the logs human readable (pretty) or as JSON. One of `pretty`, `raw`.<br>**Default: `pretty`**
 
-
 ## Database
 
 ### `DB_CLIENT`
 
-What database client to use. One of `pg` or `postgres`, `mysql`, `mysql2`, `oracledb`, `mssql`, or `sqlite3`. For all database clients except SQLite, you will also need to configure the following variables:
+What database client to use. One of `pg` or `postgres`, `mysql`, `mysql2`, `oracledb`, `mssql`, or
+`sqlite3`. For all database clients except SQLite, you will also need to configure the following
+variables:
 
 ### `DB_HOST`
 
@@ -52,12 +55,11 @@ Database user's password. Required when using `pg`, `mysql`, `mysql2`, `oracledb
 
 Where to read/write the SQLite database. Required when using `sqlite3`.
 
-::: Additional Database Variables
-All `DB_*` environment variables are passed to the `connection` configuration of a [`Knex` instance](http://knexjs.org).
-Based on your project's needs, you can extend the `DB_*` environment variables with any config you need to pass to the database instance.
+::: Additional Database Variables All `DB_*` environment variables are passed to the `connection`
+configuration of a [`Knex` instance](http://knexjs.org). Based on your project's needs, you can
+extend the `DB_*` environment variables with any config you need to pass to the database instance.
 :::
 
-
 ## Security
 
 ### `KEY`
@@ -74,7 +76,8 @@ The duration that the access token is valid.<br>**Default: `15m`**
 
 ### `REFRESH_TOKEN_TTL`
 
-The duration that the refresh token is valid, and also how long users stay logged-in to the App.<br>**Default: `7d`**
+The duration that the refresh token is valid, and also how long users stay logged-in to the
+App.<br>**Default: `7d`**
 
 ### `REFRESH_TOKEN_COOKIE_SECURE`
 
@@ -84,7 +87,6 @@ Whether or not to use a secure cookie for the refresh token in cookie mode.<br>*
 
 Value for `sameSite` in the refresh token cookie when in cookie mode.<br>**Default: `lax`**
 
-
 ## CORS
 
 ### `CORS_ENABLED`
@@ -111,7 +113,6 @@ Whether or not to send the `Access-Control-Allow-Credentials` header.<br>**Defau
 
 Value for the `Access-Control-Max-Age` header.<br>**Default: `18000`**
 
-
 ## Rate Limiting
 
 ### `RATE_LIMITER_ENABLED`
@@ -128,27 +129,28 @@ The time window in seconds in which the points are counted.<br>**Default: `1`**
 
 ### `RATE_LIMITER_STORE`
 
-Where to store the rate limiter counts. Either `memory`, `redis`, or `memcache`. Based on the rate limiter used, you must also provide the following configurations.<br>**Default: `memory`**
+Where to store the rate limiter counts. Either `memory`, `redis`, or `memcache`. Based on the rate
+limiter used, you must also provide the following configurations.<br>**Default: `memory`**
 
-* **Memory**
-	* No additional configuration required
-* **Redis**
-	* **`RATE_LIMITER_REDIS`** — Redis connection string
-		* eg: `redis://:authpassword@127.0.0.1:6380/4`
-	* Alternatively, you can enter individual connection parameters:
-		* **`RATE_LIMITER_REDIS_HOST`**
-		* **`RATE_LIMITER_REDIS_PORT`**
-		* **`RATE_LIMITER_REDIS_PASSWORD`**
-		* **`RATE_LIMITER_REDIS_DB`**
-* **Memcache**
-	* **`RATE_LIMITER_MEMCACHE`** — Location of your memcache instance
+-   **Memory**
+    -   No additional configuration required
+-   **Redis**
+    -   **`RATE_LIMITER_REDIS`** — Redis connection string
+        -   eg: `redis://:authpassword@127.0.0.1:6380/4`
+    -   Alternatively, you can enter individual connection parameters:
+        -   **`RATE_LIMITER_REDIS_HOST`**
+        -   **`RATE_LIMITER_REDIS_PORT`**
+        -   **`RATE_LIMITER_REDIS_PASSWORD`**
+        -   **`RATE_LIMITER_REDIS_DB`**
+-   **Memcache**
+    -   **`RATE_LIMITER_MEMCACHE`** — Location of your memcache instance
 
-::: Additional Rate Limiter Variables
-All `RATE_LIMITER_*` variables are passed directly to a `rate-limiter-flexible` instance. Depending on your
-project's needs, you can extend the above environment variables to configure any of [the `rate-limiter-flexible` options](https://github.com/animir/node-rate-limiter-flexible/wiki/Options).
+::: Additional Rate Limiter Variables All `RATE_LIMITER_*` variables are passed directly to a
+`rate-limiter-flexible` instance. Depending on your project's needs, you can extend the above
+environment variables to configure any of
+[the `rate-limiter-flexible` options](https://github.com/animir/node-rate-limiter-flexible/wiki/Options).
 :::
 
-
 ## Cache
 
 ### `CACHE_ENABLED`
@@ -159,9 +161,8 @@ Whether or not caching is enabled.<br>**Default: `false`**
 
 How long the cache is persisted.<br>**Default: `30m`**
 
-:::warning Forced Flush
-Regardless of TTL, the cache is always flushed for every create, update, and delete action.
-:::
+:::warning Forced Flush Regardless of TTL, the cache is always flushed for every create, update, and
+delete action. :::
 
 ### `CACHE_NAMESPACE`
 
@@ -169,57 +170,58 @@ How to scope the cache data.<br>**Default: `directus-cache`**
 
 ### `CACHE_STORE`
 
-Where to store the cache data. Either `memory`, `redis`, or `memcache`. Based on the cache used, you must also provide the following configurations.<br>**Default: `memory`**
-
-* **Memory**
-	* No additional configuration required
-* **Redis**
-	* **`CACHE_REDIS`** — Redis connection string
-		* eg: `redis://:authpassword@127.0.0.1:6380/4`
-	* Alternatively, you can enter individual connection parameters:
-		* **`CACHE_REDIS_HOST`**
-		* **`CACHE_REDIS_PORT`**
-		* **`CACHE_REDIS_PASSWORD`**
-		* **`CACHE_REDIS_DB`**
-* **Memcache**
-	* **`CACHE_MEMCACHE`** — Location of your memcache instance
+Where to store the cache data. Either `memory`, `redis`, or `memcache`. Based on the cache used, you
+must also provide the following configurations.<br>**Default: `memory`**
 
+-   **Memory**
+    -   No additional configuration required
+-   **Redis**
+    -   **`CACHE_REDIS`** — Redis connection string
+        -   eg: `redis://:authpassword@127.0.0.1:6380/4`
+    -   Alternatively, you can enter individual connection parameters:
+        -   **`CACHE_REDIS_HOST`**
+        -   **`CACHE_REDIS_PORT`**
+        -   **`CACHE_REDIS_PASSWORD`**
+        -   **`CACHE_REDIS_DB`**
+-   **Memcache**
+    -   **`CACHE_MEMCACHE`** — Location of your memcache instance
 
 ## File Storage
 
 ### `STORAGE_LOCATIONS`
 
-A CSV of storage locations (eg: `local,digitalocean,amazon`) to use. You can use any names you'd like for these keys, but each must have a matching `<LOCATION>` configuration.<br>**Default: `local`**
+A CSV of storage locations (eg: `local,digitalocean,amazon`) to use. You can use any names you'd
+like for these keys, but each must have a matching `<LOCATION>` configuration.<br>**Default:
+`local`**
 
 For each of the storage locations listed, you must provide the following configuration:
 
-* **`STORAGE_<LOCATION>_PUBLIC_URL`** — Location on the internet where the files are accessible
-* **`STORAGE_<LOCATION>_DRIVER`** — Which driver to use, either `local`, `s3`, or `gcl`
+-   **`STORAGE_<LOCATION>_PUBLIC_URL`** — Location on the internet where the files are accessible
+-   **`STORAGE_<LOCATION>_DRIVER`** — Which driver to use, either `local`, `s3`, or `gcl`
 
 Based on your configured driver, you must also provide the following configurations.
 
-* **Local**
-	* `STORAGE_<LOCATION>_ROOT` — Where to store the files on disk
-* **S3**
-	* **`STORAGE_<LOCATION>_KEY`** — User key
-	* **`STORAGE_<LOCATION>_SECRET`** — User secret
-	* **`STORAGE_<LOCATION>_ENDPOINT`** — S3 Endpoint
-	* **`STORAGE_<LOCATION>_BUCKET`** — S3 Bucket
-	* **`STORAGE_<LOCATION>_REGION`** — S3 Region
-* **Google Cloud**
-	* **`STORAGE_<LOCATION>_KEY_FILENAME`** — Path to key file on disk
-	* **`STORAGE_<LOCATION>_BUCKET`** — Google Cloud Storage bucket
-
+-   **Local**
+    -   `STORAGE_<LOCATION>_ROOT` — Where to store the files on disk
+-   **S3**
+    -   **`STORAGE_<LOCATION>_KEY`** — User key
+    -   **`STORAGE_<LOCATION>_SECRET`** — User secret
+    -   **`STORAGE_<LOCATION>_ENDPOINT`** — S3 Endpoint
+    -   **`STORAGE_<LOCATION>_BUCKET`** — S3 Bucket
+    -   **`STORAGE_<LOCATION>_REGION`** — S3 Region
+-   **Google Cloud**
+    -   **`STORAGE_<LOCATION>_KEY_FILENAME`** — Path to key file on disk
+    -   **`STORAGE_<LOCATION>_BUCKET`** — Google Cloud Storage bucket
 
 ## oAuth
 
 ### `OAUTH_PROVIDERS`
 
-CSV of oAuth providers you want to use. For each of the oAuth providers you list, you must also provide the following configurations.
-
-* **`OAUTH_<PROVIDER>_KEY`** — oAuth key for the external service
-* **`OAUTH_<PROVIDER>_SECRET`** — oAuth secret for the external service.
+CSV of oAuth providers you want to use. For each of the oAuth providers you list, you must also
+provide the following configurations.
 
+-   **`OAUTH_<PROVIDER>_KEY`** — oAuth key for the external service
+-   **`OAUTH_<PROVIDER>_SECRET`** — oAuth secret for the external service.
 
 ## Extensions
 
@@ -227,7 +229,6 @@ CSV of oAuth providers you want to use. For each of the oAuth providers you list
 
 Path to your local extensions folder.<br>**Default: `./extensions`**
 
-
 ## Email
 
 ### `EMAIL_FROM`
@@ -236,15 +237,17 @@ Email address from which emails are sent.<br>**Default: `no-reply@directus.io`**
 
 ### `EMAIL_TRANSPORT`
 
-What to use to send emails. One of `sendmail`, `smtp`. Based on the transport used, you must also provide the following configurations.<br>**Default: `sendmail`**
+What to use to send emails. One of `sendmail`, `smtp`. Based on the transport used, you must also
+provide the following configurations.<br>**Default: `sendmail`**
 
-* **Sendmail** (`sendmail`)
-	* **`EMAIL_SENDMAIL_NEW_LINE`** — What new line style to use in sendmail. **Default: `unix`**
-	* **`EMAIL_SENDMAIL_PATH`** — Path to your sendmail executable. **Default: `/usr/sbin/sendmail`**
-* **SMTP** (`smtp`)
-	* **`EMAIL_SMTP_HOST`** — SMTP Host
-	* **`EMAIL_SMTP_PORT`** — SMTP Port
-	* **`EMAIL_SMTP_USER`** — SMTP User
-	* **`EMAIL_SMTP_PASSWORD`** — SMTP Password
-	* **`EMAIL_SMTP_POOL`** — Use SMTP pooling
-	* **`EMAIL_SMTP_SECURE`** — Enable TLS
+-   **Sendmail** (`sendmail`)
+    -   **`EMAIL_SENDMAIL_NEW_LINE`** — What new line style to use in sendmail. **Default: `unix`**
+    -   **`EMAIL_SENDMAIL_PATH`** — Path to your sendmail executable. **Default:
+        `/usr/sbin/sendmail`**
+-   **SMTP** (`smtp`)
+    -   **`EMAIL_SMTP_HOST`** — SMTP Host
+    -   **`EMAIL_SMTP_PORT`** — SMTP Port
+    -   **`EMAIL_SMTP_USER`** — SMTP User
+    -   **`EMAIL_SMTP_PASSWORD`** — SMTP Password
+    -   **`EMAIL_SMTP_POOL`** — Use SMTP pooling
+    -   **`EMAIL_SMTP_SECURE`** — Enable TLS
diff --git a/docs/reference/error-codes.md b/docs/reference/error-codes.md
index 6f6d1ea233..2b22ef7812 100644
--- a/docs/reference/error-codes.md
+++ b/docs/reference/error-codes.md
@@ -1,7 +1,7 @@
 # Error Codes
 
 | Error Code            | Description                                    |
-|-----------------------|------------------------------------------------|
+| --------------------- | ---------------------------------------------- |
 | `FAILED_VALIDATION`   | Validation for this particular item failed     |
 | `FORBIDDEN`           | You are not allowed to do the current action   |
 | `INVALID_CREDENTIALS` | Username / password or access token is wrong   |
@@ -12,6 +12,5 @@
 | `ROUTE_NOT_FOUND`     | Endpoint does not exist                        |
 | `SERVICE_UNAVAILABLE` | Could not use external service                 |
 
-:::warning Security
-To prevent leaking which items exist, all actions for non-existing items will return a `FORBIDDEN` error.
-:::
+:::warning Security To prevent leaking which items exist, all actions for non-existing items will
+return a `FORBIDDEN` error. :::
diff --git a/docs/reference/filter-rules.md b/docs/reference/filter-rules.md
index 151f135eb2..23a1827793 100644
--- a/docs/reference/filter-rules.md
+++ b/docs/reference/filter-rules.md
@@ -1,12 +1,14 @@
 # Filter Rules
 
-> Permissions, validation, and the API's `filter` parameter all rely on a specific JSON structure to define their rules. This page describes the syntax for creating flat, relational, or complex filter rules.
+> Permissions, validation, and the API's `filter` parameter all rely on a specific JSON structure to
+> define their rules. This page describes the syntax for creating flat, relational, or complex
+> filter rules.
 
 ## Syntax
 
-* **Field** — Any valid root field, [relational field](#), or [logical operator](#)
-* **Operator** — Any valid [API operator](#) prefaced with an underscore
-* **Value** — Any valid static value, or [dynamic variable](#)
+-   **Field** — Any valid root field, [relational field](#), or [logical operator](#)
+-   **Operator** — Any valid [API operator](#) prefaced with an underscore
+-   **Value** — Any valid static value, or [dynamic variable](#)
 
 ```
 {
@@ -44,33 +46,34 @@
 
 ## Supported Operators
 
-| Operator             | Description                            |
-| -------------------- | -------------------------------------- |
-| `eq`                 | Equal to                               |
-| `neq`                | Not equal to                           |
-| `lt`                 | Less than                              |
-| `lte`                | Less than or equal to                  |
-| `gt`                 | Greater than                           |
-| `gte`                | Greater than or equal to               |
-| `in`                 | Exists in one of the values            |
-| `nin`                | Not in one of the values               |
-| `null`               | It is null                             |
-| `nnull`              | It is not null                         |
-| `contains`, `like`   | Contains the substring                 |
-| `ncontains`, `nlike` | Doesn't contain the substring          |
-| `rlike`              | Contains a substring using a wildcard  |
+| Operator             | Description                               |
+| -------------------- | ----------------------------------------- |
+| `eq`                 | Equal to                                  |
+| `neq`                | Not equal to                              |
+| `lt`                 | Less than                                 |
+| `lte`                | Less than or equal to                     |
+| `gt`                 | Greater than                              |
+| `gte`                | Greater than or equal to                  |
+| `in`                 | Exists in one of the values               |
+| `nin`                | Not in one of the values                  |
+| `null`               | It is null                                |
+| `nnull`              | It is not null                            |
+| `contains`, `like`   | Contains the substring                    |
+| `ncontains`, `nlike` | Doesn't contain the substring             |
+| `rlike`              | Contains a substring using a wildcard     |
 | `nrlike`             | Not contains a substring using a wildcard |
-| `between`            | The value is between two values        |
-| `nbetween`           | The value is not between two values    |
-| `empty`              | The value is empty (null or falsy)     |
-| `nempty`             | The value is not empty (null or falsy) |
-| `all`                | Contains all given related item's IDs  |
-| `has`                | Has one or more related items's IDs    |
+| `between`            | The value is between two values           |
+| `nbetween`           | The value is not between two values       |
+| `empty`              | The value is empty (null or falsy)        |
+| `nempty`             | The value is not empty (null or falsy)    |
+| `all`                | Contains all given related item's IDs     |
+| `has`                | Has one or more related items's IDs       |
 
 ## Relational
 
-You can target related values by nesting field names. For example, if you have a relational [Many-to-One](#)
-`author` field, you can set a rule for the `author.name` field using the following syntax.
+You can target related values by nesting field names. For example, if you have a relational
+[Many-to-One](#) `author` field, you can set a rule for the `author.name` field using the following
+syntax.
 
 ```json
 {
@@ -84,52 +87,49 @@ You can target related values by nesting field names. For example, if you have a
 
 ## Logical Operators
 
-You can nest or group multiple rules using the `_and` or `_or` logical operators. Each operator holds an array of rules, allowing for more complex filtering.
+You can nest or group multiple rules using the `_and` or `_or` logical operators. Each operator
+holds an array of rules, allowing for more complex filtering.
 
 ```json
 {
-  "_or": [
-    {
-      "_and": [
-        {
-          "owner": {
-            "_eq": "$CURRENT_USER"
-          }
-        },
-        {
-          "status": {
-            "_in": [
-              "published",
-              "draft"
-            ]
-          }
-        }
-      ]
-    },
-    {
-      "_and": [
-        {
-          "owner": {
-            "_neq": "$CURRENT_USER"
-          }
-        },
-        {
-          "status": {
-            "_in": [
-              "published"
-            ]
-          }
-        }
-      ]
-    }
-  ]
+	"_or": [
+		{
+			"_and": [
+				{
+					"owner": {
+						"_eq": "$CURRENT_USER"
+					}
+				},
+				{
+					"status": {
+						"_in": ["published", "draft"]
+					}
+				}
+			]
+		},
+		{
+			"_and": [
+				{
+					"owner": {
+						"_neq": "$CURRENT_USER"
+					}
+				},
+				{
+					"status": {
+						"_in": ["published"]
+					}
+				}
+			]
+		}
+	]
 }
 ```
 
 ## Dynamic Variables
 
-In addition to static values, you can also filter against _dynamic_ values using the following variables.
+In addition to static values, you can also filter against _dynamic_ values using the following
+variables.
 
-* `$CURRENT_USER` — The primary key of the currently authenticated user
-* `$CURRENT_ROLE` — The primary key of the role for the currently authenticated user
-* `$NOW` — The current timestamp
+-   `$CURRENT_USER` — The primary key of the currently authenticated user
+-   `$CURRENT_ROLE` — The primary key of the role for the currently authenticated user
+-   `$NOW` — The current timestamp
diff --git a/docs/reference/item-objects.md b/docs/reference/item-objects.md
index 02e8c0c473..35aff08cb6 100644
--- a/docs/reference/item-objects.md
+++ b/docs/reference/item-objects.md
@@ -4,8 +4,8 @@
 
 ## Syntax
 
-* **Field** — Any valid root field or [relational field](#)
-* **Value** — Any valid static value, or [dynamic variable](#)
+-   **Field** — Any valid root field or [relational field](#)
+-   **Value** — Any valid static value, or [dynamic variable](#)
 
 ```
 {
@@ -23,8 +23,9 @@
 
 ## Relational
 
-You can set related values by nesting field names. For example, if you have a relational [Many-to-One](#)
-`author` field, you can set a rule for the `author.name` field using the following syntax.
+You can set related values by nesting field names. For example, if you have a relational
+[Many-to-One](#) `author` field, you can set a rule for the `author.name` field using the following
+syntax.
 
 ```json
 {
@@ -38,6 +39,6 @@ You can set related values by nesting field names. For example, if you have a re
 
 In addition to static values, you can also set _dynamic_ values using the following variables.
 
-* `$CURRENT_USER` — The primary key of the currently authenticated user
-* `$CURRENT_ROLE` — The primary key of the role for the currently authenticated user
-* `$NOW` — The current timestamp
+-   `$CURRENT_USER` — The primary key of the currently authenticated user
+-   `$CURRENT_ROLE` — The primary key of the role for the currently authenticated user
+-   `$NOW` — The current timestamp
diff --git a/docs/reference/sdk-js.md b/docs/reference/sdk-js.md
index e3660bce20..cf2ca4c983 100644
--- a/docs/reference/sdk-js.md
+++ b/docs/reference/sdk-js.md
@@ -1,6 +1,7 @@
 # SDK JS
 
-The JS SDK is a small wrapper around [Axios](https://npmjs.com/axios) that makes it a little easier to use the Directus API from a JavaScript powered project.
+The JS SDK is a small wrapper around [Axios](https://npmjs.com/axios) that makes it a little easier
+to use the Directus API from a JavaScript powered project.
 
 ## Installation
 
@@ -56,7 +57,7 @@ const directus = new DirectusSDK('https://api.example.com/', {
 		storage: new MemoryStore(), // Storage adapter where refresh tokens are stored in JSON mode
 		mode: 'json', // What login mode to use. One of `json`, `cookie`
 		autoRefresh: true, // Whether or not to automatically refresh the access token on login
-	}
+	},
 });
 ```
 
@@ -85,18 +86,19 @@ You can tap into the Axios instance used directly through `directus.axios`.
 
 ```js
 directus.items('articles').create({
-	title: 'My New Article'
+	title: 'My New Article',
 });
 ```
 
 ##### Multiple Items
+
 ```js
 directus.items('articles').create([
 	{
-		title: 'My First Article'
+		title: 'My First Article',
 	},
 	{
-		title: 'My Second Article'
+		title: 'My Second Article',
 	},
 ]);
 ```
@@ -116,9 +118,9 @@ directus.items('articles').read({
 	search: 'Directus',
 	filter: {
 		date_published: {
-			_gte: '$NOW'
-		}
-	}
+			_gte: '$NOW',
+		},
+	},
 });
 ```
 
@@ -149,29 +151,21 @@ directus.items('articles').read([15, 42], { fields: ['title'] });
 ```js
 // One
 directus.items('articles').update(15, {
-	title: 'An Updated title'
+	title: 'An Updated title',
 });
 
 // Multiple
 directus.items('articles').update([15, 42], {
-	title: 'An Updated title'
+	title: 'An Updated title',
 });
 ```
 
 Supports optional query:
 
 ```js
-directus.items('articles').update(
-	15,
-	{ title: 'An Updated title' },
-	{ fields: ['title'] }
-);
+directus.items('articles').update(15, { title: 'An Updated title' }, { fields: ['title'] });
 
-directus.items('articles').update(
-	[15, 42],
-	{ title: 'An Updated title' },
-	{ fields: ['title'] }
-);
+directus.items('articles').update([15, 42], { title: 'An Updated title' }, { fields: ['title'] });
 ```
 
 ##### Multiple Items, Multiple Values
@@ -192,16 +186,19 @@ directus.items('articles').update([
 Supports optional query:
 
 ```js
-directus.items('articles').update([
-	{
-		id: 15,
-		title: 'Article 15',
-	},
-	{
-		id: 42,
-		title: 'Article 42',
-	},
-], { fields: ['title'] });
+directus.items('articles').update(
+	[
+		{
+			id: 15,
+			title: 'Article 15',
+		},
+		{
+			id: 42,
+			title: 'Article 42',
+		},
+	],
+	{ fields: ['title'] }
+);
 ```
 
 ##### Multiple Items by Query, Single Value
@@ -209,14 +206,14 @@ directus.items('articles').update([
 ```js
 directus.items('articles').update(
 	{
-		archived: true
+		archived: true,
 	},
 	{
 		filter: {
 			publish_date: {
-				_gte: '$NOW'
-			}
-		}
+				_gte: '$NOW',
+			},
+		},
 	}
 );
 ```
@@ -249,9 +246,9 @@ directus.activity.read();
 directus.activity.read({
 	filter: {
 		action: {
-			_eq: 'create'
-		}
-	}
+			_eq: 'create',
+		},
+	},
 });
 ```
 
@@ -281,7 +278,7 @@ directus.activity.read([15, 42], { fields: ['action'] });
 directus.activity.comments.create({
 	collection: 'articles',
 	item: 15,
-	comment: 'Hello, world!'
+	comment: 'Hello, world!',
 });
 ```
 
@@ -311,13 +308,19 @@ Note: these configuration options are passed in the top level SDK constructor.
 
 ##### mode
 
-`cookie` or `json`. When in cookie mode, the API will set the refresh token in a `httpOnly` secure cookie that can't be accessed from client side JS. This is the most secure way to connect to the API from a public front-end website.
+`cookie` or `json`. When in cookie mode, the API will set the refresh token in a `httpOnly` secure
+cookie that can't be accessed from client side JS. This is the most secure way to connect to the API
+from a public front-end website.
 
-When you can't rely on cookies, or need more control over handling the storage of the cookie, use `json` mode. This will return the refresh token like "regular" in the payload. You can use the `storage` option (see below) to control where the refresh token is stored / read from
+When you can't rely on cookies, or need more control over handling the storage of the cookie, use
+`json` mode. This will return the refresh token like "regular" in the payload. You can use the
+`storage` option (see below) to control where the refresh token is stored / read from
 
 ##### storage
 
-When using `json` for mode, the refresh token needs to be stored somewhere. The `storage` option allows you to plug in any object that has an async `setItem()` and `getItem()` method. This allows you to plugin things like [`localforage`](https://github.com/localForage/localForage) directly:
+When using `json` for mode, the refresh token needs to be stored somewhere. The `storage` option
+allows you to plug in any object that has an async `setItem()` and `getItem()` method. This allows
+you to plugin things like [`localforage`](https://github.com/localForage/localForage) directly:
 
 ```js
 import localforage from 'localforage';
@@ -328,7 +331,8 @@ const directus = new DirectusSDK('https://api.example.com', { storage: localfora
 
 ##### autoRefresh
 
-Whether or not to automatically call `refresh()` when the access token is about to expire. Defaults to `true`
+Whether or not to automatically call `refresh()` when the access token is about to expire. Defaults
+to `true`
 
 #### Get / Set Token
 
@@ -473,7 +477,7 @@ directus.server.specs.oas();
 #### Ping the Server
 
 ```js
-directus.server.ping()
+directus.server.ping();
 ```
 
 #### Get Server/Project Info
@@ -540,7 +544,7 @@ Supports optional query:
 
 ```js
 directus.users.me.read({
-	fields: ['last_access']
+	fields: ['last_access'],
 });
 ```
 
@@ -553,10 +557,7 @@ directus.users.me.update({ first_name: 'Admin' });
 Supports optional query:
 
 ```js
-directus.users.me.update(
-	{ first_name: 'Admin' },
-	{ fields: ['last_access'] }
-);
+directus.users.me.update({ first_name: 'Admin' }, { fields: ['last_access'] });
 ```
 
 ---