data fetching + narrow widths

Author: ryanfoxtyler

.trunk/configs/.prettierrc.yaml

@@ -1,3 +1,3 @@
 semi: false
 proseWrap: always
-printWidth: 120
+printWidth: 100

README.md

@@ -1,18 +1,20 @@
 # Docs
 
-Self-serve documentation is a critical part of any technical product. Beyond current users, docs are an important
-evaluation tool for prospective users.
+Self-serve documentation is a critical part of any technical product. Beyond current users, docs are
+an important evaluation tool for prospective users.
 
 ## Source Control
 
-Our docs are maintained in markdown files in this repo. All changes are managed through a code-first release flow.
+Our docs are maintained in markdown files in this repo. All changes are managed through a code-first
+release flow.
 
 ## Hosting
 
-The design and hosting of our site is provided by [Mintlify](https://mintlify.com/). The vast majority of configuration
-is in code in `mint.json`.
+The design and hosting of our site is provided by [Mintlify](https://mintlify.com/). The vast
+majority of configuration is in code in `mint.json`.
 
-Changes will be deployed to [production](https://docs.hypermode.com) automatically after pushing to the `main` branch.
+Changes will be deployed to [production](https://docs.hypermode.com) automatically after pushing to
+the `main` branch.
 
 ## Development Environment Setup
 
@@ -48,8 +50,8 @@ npm i -g @trunkio/launcher
 
 ## Writing
 
-Mintlify includes a [number of components](https://mintlify.com/docs/content/components/accordions) to make it easier to
-build easy-to-consume documentation.
+Mintlify includes a [number of components](https://mintlify.com/docs/content/components/accordions)
+to make it easier to build easy-to-consume documentation.
 
 To spin up a local server, run the following command at the root of the docs repo:
 
@@ -59,31 +61,33 @@ mintlify dev
 
 ### Style
 
-Consistency is important in any documentation experience. Beyond Markdown’s opinionated structure, we adhere to a
-consistent style for Hypermode.
+Consistency is important in any documentation experience. Beyond Markdown’s opinionated structure,
+we adhere to a consistent style for Hypermode.
 
-We have adopted [Google’s Developer Documentation Style Guide](https://developers.google.com/style/) as a baseline, with
-Hypermode-specific terms [stored in a vocabulary file](./styles/config/vocabularies/general/accept.txt).
+We have adopted [Google’s Developer Documentation Style Guide](https://developers.google.com/style/)
+as a baseline, with Hypermode-specific terms
+[stored in a vocabulary file](./styles/config/vocabularies/general/accept.txt).
 
-[Vale](https://vale.sh/) has been implemented in the repo for easy alignment. Vale is implemented within CI/CD, but also
-executable locally with:
+[Vale](https://vale.sh/) has been implemented in the repo for easy alignment. Vale is implemented
+within CI/CD, but also executable locally with:
 
 ```bash
 vale --glob='*.{mdx}' *
 ```
 
-A [Vale VS Code extension](https://marketplace.visualstudio.com/items?itemName=ChrisChinchilla.vale-vscode) is also
-available, and is included in the recommended extensions for this repo.
+A
+[Vale VS Code extension](https://marketplace.visualstudio.com/items?itemName=ChrisChinchilla.vale-vscode)
+is also available, and is included in the recommended extensions for this repo.
 
 ### Iconography
 
-When icons are required, select from [Font Awesome](https://fontawesome.com/icons)’s catalog for easy rendering with
-Mintlify.
+When icons are required, select from [Font Awesome](https://fontawesome.com/icons)’s catalog for
+easy rendering with Mintlify.
 
 ### Formatting and Linting
 
-Trunk has been implemented for easy formatting and linting across different file types. It is implemented within CI/CD,
-but also executable locally.
+Trunk has been implemented for easy formatting and linting across different file types. It is
+implemented within CI/CD, but also executable locally.
 
 To format the repo locally, run:
 
@@ -97,10 +101,11 @@ To run lint checks, run:
 trunk check # appending --all will run checks beyond changes on the current branch
 ```
 
-Note that Trunk also has a [VS Code extension](https://marketplace.visualstudio.com/items?itemName=Trunk.io) you can
-install.
+Note that Trunk also has a
+[VS Code extension](https://marketplace.visualstudio.com/items?itemName=Trunk.io) you can install.
 
-However, when installing it please be aware of the `trunk.autoInit` setting, which is `true` (enabled) by default This
-controls whether to auto-initialize trunk in non-trunk repositories - meaning _any_ folder you open with VS Code will
-get configured with a `.trunk` subfolder, and will start using Trunk. You should probably set this to `false` in your VS
-Code user settings, to not interfere with other projects you may be working on.
+However, when installing it please be aware of the `trunk.autoInit` setting, which is `true`
+(enabled) by default This controls whether to auto-initialize trunk in non-trunk repositories -
+meaning _any_ folder you open with VS Code will get configured with a `.trunk` subfolder, and will
+start using Trunk. You should probably set this to `false` in your VS Code user settings, to not
+interfere with other projects you may be working on.

community-and-support.mdx

@@ -3,27 +3,30 @@ title: Community and Support
 description: "Get help with Hypermode and connect with other developers"
 ---
 
-Whether you're just getting started or you're a seasoned developer, we're here to help you every step of the way. We’re
-excited to have you as part of the Hypermode community and look forward to seeing what you build!
+Whether you're just getting started or you're a seasoned developer, we're here to help you every
+step of the way. We’re excited to have you as part of the Hypermode community and look forward to
+seeing what you build!
 
 ## Community
 
-[Discord](https://discord.hypermode.com) is our main forum where you can ask questions, share your knowledge, and
-connect with other developers.
+[Discord](https://discord.hypermode.com) is our main forum where you can ask questions, share your
+knowledge, and connect with other developers.
 
 ## Getting help
 
-If you encounter a bug or have a feature request, you can open an issue on the relevant GitHub repository:
+If you encounter a bug or have a feature request, you can open an issue on the relevant GitHub
+repository:
 
 - [Modus](https://github.com/hypermodeinc/modus/issues)
 - [Hyp CLI](https://github.com/hypermodeinc/hyp-cli/issues)
 
-All paid Hypermode packages include commercial support. Customers can reach out via the Hypermode Console or through
-email at [[email protected]](mailto:[email protected]).
+All paid Hypermode packages include commercial support. Customers can reach out via the Hypermode
+Console or through email at [[email protected]](mailto:[email protected]).
 
 ## Stay connected
 
 Stay up-to-date with the latest news, updates, and announcements from Hypermode:
 
 - **[X](https://x.com/hypermodeinc)**: follow us on X for the latest news and updates
-- **[Blog](https://hypermode.com/blog)**: explore our blog for in-depth articles, tutorials, and case studies
+- **[Blog](https://hypermode.com/blog)**: explore our blog for in-depth articles, tutorials, and
+  case studies

configure-environment.mdx

@@ -3,21 +3,22 @@ title: Configure Environment
 description: "Define environment parameters for your app"
 ---
 
-On your first deployment, and when you add new hosts thereafter, you may need to adjust the configuration of your
-environment for your app to be ready for traffic.
+On your first deployment, and when you add new hosts thereafter, you may need to adjust the
+configuration of your environment for your app to be ready for traffic.
 
 ## Host secrets
 
-If you included parameters for Host Secrets in your [app manifest](/modus/app-manifest), you'll need to add the
-parameter values in the Hypermode Console.
+If you included parameters for Host Secrets in your [app manifest](/modus/app-manifest), you'll need
+to add the parameter values in the Hypermode Console.
 
-From your project home, navigate to **Settings** → **Hosts**. Add the values for your defined host authentication
-parameters.
+From your project home, navigate to **Settings** → **Hosts**. Add the values for your defined host
+authentication parameters.
 
 ## Model hosting
 
-Where available, Hypermode defaults to shared model instances. If your app requires dedicated instances, refer to the
-[Hosted Models](/hosted-models) documentation for instructions on setting up dedicated models.
+Where available, Hypermode defaults to shared model instances. If your app requires dedicated
+instances, refer to the [Hosted Models](/hosted-models) documentation for instructions on setting up
+dedicated models.
 
 ## Scaling your runtime resources
 

create-project.mdx

@@ -3,29 +3,29 @@ title: Create Project
 description: "Initialize your Modus app with Hypermode"
 ---
 
-A Hypermode project represents your Modus app and associated models. You can create a project through the Hypermode
-Console or Hyp CLI.
+A Hypermode project represents your Modus app and associated models. You can create a project
+through the Hypermode Console or Hyp CLI.
 
 ## Create with Hypermode Console
 
 <Note>
-  Hypermode relies on git as a source for project deployment. Through the project creation flow, you'll connect
-  Hypermode to your GitHub account.
+  Hypermode relies on git as a source for project deployment. Through the project creation flow,
+  you'll connect Hypermode to your GitHub account.
 </Note>
 
 From your organization home, click **New Project**. Set a name for the project and click **Create**.
 
-Once you have created a project, Hypermode prompts you to import the repo with your Modus app. To create your first
-Modus app, see the [Modus quickstart](modus/quickstart).
+Once you have created a project, Hypermode prompts you to import the repo with your Modus app. To
+create your first Modus app, see the [Modus quickstart](modus/quickstart).
 
 ## Import with Hyp CLI
 
-After you have created your Modus app, you can initialize the app with Hypermode through the Hyp CLI. To initialize your
-Hypermode project, run
+After you have created your Modus app, you can initialize the app with Hypermode through the Hyp
+CLI. To initialize your Hypermode project, run
 
 ```bash
 hyp init
 ```
 
-This command adds a default GitHub Actions workflow to build your Modus app and a Hypermode GitHub app for
-auto-deployment. Once initialized, each commit to the target branch triggers a deployment.
+This command adds a default GitHub Actions workflow to build your Modus app and a Hypermode GitHub
+app for auto-deployment. Once initialized, each commit to the target branch triggers a deployment.

deploy.mdx

@@ -3,19 +3,21 @@ title: Deploy Project
 description: "A git-based flow for simple deployment"
 ---
 
-Hypermode features a native GitHub integration for the deployment of Hypermode projects. The deployment includes your
-Modus app as well as any models defined in the [app manifest](/modus/app-manifest).
+Hypermode features a native GitHub integration for the deployment of Hypermode projects. The
+deployment includes your Modus app as well as any models defined in the
+[app manifest](/modus/app-manifest).
 
 <Note>Preview environments for live validation of pull requests are in development.</Note>
 
 ## Build
 
-When you initialize your project with Hypermode, the Hyp CLI adds a GitHub Actions workflow to your repo that builds
-your Modus app to Hypermode on commit.
+When you initialize your project with Hypermode, the Hyp CLI adds a GitHub Actions workflow to your
+repo that builds your Modus app to Hypermode on commit.
 
 ## Deploy
 
 On successful build of your project, Hypermode automatically deploys your project changes. For
-[hosted models](/hosted-models), Hypermode creates a connection for your app to a shared or dedicated model instance.
+[hosted models](/hosted-models), Hypermode creates a connection for your app to a shared or
+dedicated model instance.
 
 You can view the deployment status from the Deployment tab within the Hypermode Console.