Add Node.js version requirement for CLI

installation.mdx

@@ -1,6 +1,6 @@
 ---
 title: "CLI installation"
-description: "Install the CLI to preview and develop your docs locally"
+description: "Use the CLI to preview and maintain your documentation locally"
 ---
 
 <img
@@ -14,14 +14,18 @@
   alt="Decorative graphic representing the CLI."
 />
 
-## Installing the CLI
+Use the CLI to preview your documentation locally as you write and edit. View changes in real-time before deploying, test your documentation site's appearance and functionality, and catch issues like broken links or accessibility problems.
+
+The CLI also has utilities for maintaining your documentation, including commands to rename files, validate OpenAPI specifications, and migrate content between formats.
+
+## Install the CLI
 
 <Info>
-  **Prerequisite**: Please install [Node.js](https://nodejs.org/en) before proceeding.
+  **Prerequisite**: The CLI requires [Node.js](https://nodejs.org/en) v19 or higher.
 </Info>
 
 <Steps>
-  <Step title="Install the CLI.">
+  <Step title="Install the CLI">
     Run the following command to install the [CLI](https://www.npmjs.com/package/mint):
 
   <CodeGroup>
@@ -35,8 +39,8 @@
   </CodeGroup>
 
   </Step>
-  <Step title="Preview locally.">
+  <Step title="Preview locally">
     Navigate to your docs directory (where your `docs.json` file is located) and execute the following command:
 
     ```bash
     mint dev
@@ -46,7 +50,7 @@
   </Step>
 </Steps>
 
 Alternatively, if you do not want to install the CLI globally, you can run a one-time script:
 
 ```bash
 npx mint dev
@@ -54,13 +58,13 @@
 
 ## Updates
 
 If your local preview is out of sync with what you see on the web in the production version, update your local CLI:
 
 ```bash
 mint update
 ```
 
 If this `mint update` command is not available on your local version, re-install the CLI with the latest version:
 
  <CodeGroup>
     ```bash npm
@@ -74,19 +78,19 @@
 
 ## Custom ports
 
 By default, the CLI uses port 3000. You can customize the port using the `--port` flag. To run the CLI on port 3333, for instance, use this command:
 
 ```bash
 mint dev --port 3333
 ```
 
 If you attempt to run on a port that is already in use, it will use the next available port:
 
 ```mdx
 Port 3000 is already in use. Trying 3001 instead.
 ```
 
-## Previewing as a specific group
+## Preview as a specific group
 
 If you use partial authentication to restrict access to your documentation, you can preview as a specific authentication group by using the `--groups [groupname]` flag.
 
@@ -122,7 +126,7 @@
 mint openapi-check <OpenAPI filename or URL>
 ```
 
 Pass a filename (for example, `./openapi.yaml`) or a URL (for example, `https://petstore3.swagger.io/api/v3/openapi.json`).
 
 ### Rename files
 
@@ -144,11 +148,11 @@
 
 ## Formatting
 
 While developing locally, we recommend using extensions in your IDE to recognize and format `MDX` files.
 
 If you use Cursor, Windsurf, or VS Code, we recommend the [MDX VS Code extension](https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx) for syntax highlighting, and [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) for code formatting.
 
 If you use JetBrains, we recommend the [MDX IntelliJ IDEA plugin](https://plugins.jetbrains.com/plugin/14944-mdx) for syntax highlighting, and setting up [Prettier](https://prettier.io/docs/webstorm) for code formatting.
 
 ## Troubleshooting
 
@@ -161,7 +165,7 @@
     3. Reinstall the mint CLI: `npm install -g mint`
   </Accordion>
   <Accordion title="Issue: Encountering an unknown error">
     **Solution**: Go to the root of your device and delete the `~/.mintlify` folder. Afterwards, run `mint dev` again.
   </Accordion>
   <Accordion title="Error: permission denied">
     This is due to not having the required permissions to globally install node packages.
@@ -169,12 +173,12 @@
     **Solution**: Try running `sudo npm i -g mint`. You will be prompted for your password, which is the one you use to unlock your computer.
   </Accordion>
   <Accordion title="The local preview doesn't look the same as my docs do on the web">
     This is likely due to an outdated version of the CLI.
 
    **Solution:** Run `mint update` to get the latest changes.
   </Accordion>
   <Accordion title="mintlify vs. mint package">
     If you have any problems with the CLI package, you should first run `npm ls -g`. This command shows what packages are globally installed on your machine.
 
     If you don't use npm or don't see it in the -g list, try `which mint` to locate the installation.
 

quickstart.mdx

@@ -5,11 +5,11 @@
 
 This quickstart guide shows you how to set up and deploy your documentation site in minutes.
 
 After completing this guide, you will have a live documentation site ready to customize and expand.
 
 <Info>
 
 **Prerequisites**: Before you begin, [create an account](https://mintlify.com/start) and complete onboarding.
 
 </Info>
 
@@ -30,7 +30,7 @@
 
 Your site's URL is available immediately. Use this URL for testing and sharing with your team while you are setting up your docs site.
 
 ### Install the GitHub App
 
 Mintlify provides a GitHub App that automates deployment when you push changes to your repository.
 
@@ -54,11 +54,11 @@
 ### Authorize your GitHub account
 
 1. Navigate to **Settings** in your Mintlify dashboard.
 2. Select **My Profile** from the sidebar.
 3. Select **Authorize GitHub account**. This opens a new tab to the GitHub authorization page.
 
 <Info>
   An admin for your GitHub organization may need to authorize your account depending on your organization settings.
 </Info>
 
 ## Editing workflows
@@ -77,9 +77,13 @@
 
 The code-based workflow integrates with your existing development environment and Git repositories. This workflow is best for technical teams who want to manage documentation alongside code.
 
 ### Install the CLI
 
+<Info>
+  **Prerequisite**: The CLI requires [Node.js](https://nodejs.org/en) v19 or higher.
+</Info>
+
 To work locally with your documentation, install the Command Line Interface (CLI), called [mint](https://www.npmjs.com/package/mint), by running this command in your terminal:
 
 <CodeGroup>
   ```bash npm
@@ -91,10 +95,6 @@
   ```
 </CodeGroup>
 
-<Info>
-  You need Node.js installed on your machine. If you encounter installation issues, check the troubleshooting guide.
-</Info>
-
 ### Edit the documentation
 
 After setting up your environment, you can start editing your documentation files. For example, update the title of the introduction page:
@@ -126,7 +126,7 @@
 mint dev
 ```
 
 Your preview will be available at `localhost:3000`.
 
 <Frame>
   <img src="/images/quickstart/mintlify-dev-light.png" alt="Mintlify Dev" className="block dark:hidden" />
@@ -139,7 +139,7 @@
 
 Mintlify automatically detects the changes, builds your documentation, and deploys the updates to your site. Monitor the deployment status in your GitHub repository commit history or the [dashboard](https://dashboard.mintlify.com).
 
 After the deployment completes, your latest update will be available at `<your-project-name>.mintlify.app`.
 
 <Card title="Jump to adding a custom domain" icon="arrow-down" href="#adding-a-custom-domain" horizontal>
   Optionally, skip the web editor workflow and jump to adding a custom domain.
@@ -147,7 +147,7 @@
 
 ## Web editor workflow
 
 The web editor workflow provides a what-you-see-is-what-you-get (WYSIWYG) interface for creating and editing documentation. This workflow is best for people who want to work in their web browser without additional local development tools.
 
 ### Access the web editor
 
@@ -155,7 +155,7 @@
 2. Select **Editor** on the left sidebar.
 
 <Info>
   If you have not installed the GitHub App, you will be prompted to install the app when you open the web editor.
 </Info>
 
 <Frame>
@@ -165,11 +165,11 @@
 
 ### Edit the documentation
 
 In the web editor, you can navigate through your documentation files in the sidebar. Let's update the introduction page:
 
 Find and select `index.mdx` in the file explorer.
 
 Then, in the editor, update the title field to "Hello World".
 
 <Frame>
   <img alt="Editing in Web Editor" src="/images/quickstart/web-editor-editing-light.png" className="block dark:hidden" />
@@ -188,7 +188,7 @@
   Use branches to preview and review changes through pull requests before deploying to your live site.
 </Tip>
 
 For more details about using the web editor, including using branches and pull requests to collaborate and preview changes, see our [web editor documentation](/editor).
 
 ## Adding a custom domain
 
@@ -201,21 +201,21 @@
   <img src="/images/quickstart/custom-domain-dark.png" alt="Custom Domain" className="hidden dark:block" />
 </Frame>
 
 Enter your domain (for example, `docs.yourcompany.com`) and follow the provided instructions to configure DNS settings with your domain provider.
 
 <Table>
 | Record Type | Name | Value | TTL |
 |-------------|------|-------|-----|
 | CNAME | docs (or subdomain) | cname.mintlify.app | 3600 |
 </Table>
 
 <Info>
   DNS changes can take up to 48 hours to propagate, though changes often complete much sooner.
 </Info>
 
 ## Next steps
 
 Congratulations! You have successfully deployed your documentation site with Mintlify. Here are suggested next steps to enhance your documentation:
 
 <Card title="Configure your global settings" icon="settings" href="organize/settings" horizontal>
   Configure site-wide styling, navigation, integrations, and more with the `docs.json` file.
@@ -245,6 +245,6 @@
     Deployment can take upwards to a few minutes. Check your GitHub Actions (for code-based workflow) or deployment logs in the Mintlify dashboard to ensure there are no build errors.
   </Accordion>
   <Accordion title="Custom domain not connecting">
     Verify that your DNS records are set up correctly and allow sufficient time for DNS propagation (up to 48 hours). You can use tools like [DNSChecker](https://dnschecker.org) to verify your CNAME record.
   </Accordion>
 </AccordionGroup>