remove navigation content

Author: ethanpalm

api-playground/mdx/configuration.mdx

@@ -3,7 +3,7 @@ title: 'MDX setup'
 description: 'Generate docs pages for your API endpoints using `MDX`'
 ---
 
-You can manually define API endpoints in individual `MDX` files rather than using an OpenAPI specification. This method provides flexibility for custom content, but we recommend generating API documentation from an OpenAPI specification file for most projects because it is more maintainable and feature-rich. However, creating `MDX` pages for an API can be useful to document small APIs or for prototyping.
+You can manually define API endpoints in individual `MDX` files rather than using an OpenAPI specification. This method provides flexibility for custom content, but we recommend generating API documentation from an OpenAPI specification file for most projects because it is more maintainable and feature-rich. However, creating `MDX` pages for an API can be useful to document small APIs, prototyping, or when you want more control over where API endpoints are in the navigation.
 
 To generate pages for API endpoints using `MDX`, configure your API settings in `docs.json`, create individual `MDX` files for each endpoint, and use components like `<ParamFields />` to define parameters. From these definitions, Mintlify generates interactive API playgrounds, request examples, and response examples.
 

api-playground/migrating-from-mdx.mdx

@@ -185,9 +185,7 @@ When `x-mint: href` is present, the navigation entry will link directly to the s
 
 ## Auto-populate API pages
 
-Add an `openapi` field to any navigation element in your `docs.json` to automatically generate pages for OpenAPI endpoints. You can control where these pages appear in your navigation structure, as dedicated API sections or with other pages.
-
-The `openapi` field accepts either a file path in your docs repo or a URL to a hosted OpenAPI document.
+Add an `openapi` field to any navigation element in your `docs.json` to automatically generate pages for OpenAPI endpoints. The `openapi` field accepts either a file path in your docs repo or a URL to a hosted OpenAPI document.
 
 Generated endpoint pages have these default metadata values:
 
@@ -252,92 +250,9 @@ You can use multiple OpenAPI specifications in different navigation sections:
   The `directory` field is optional and specifies where generated API pages are stored in your docs repo. If not specified, defaults to the `api-reference` directory of your repo.
 </Note>
 
-### Selective endpoints
-
-When you want more control over which endpoints appear where in your documentation, you can reference specific endpoints in your navigation. This approach allows you to mix API endpoints with other documentation pages.
-
-#### Set a default OpenAPI spec
-
-Configure a default OpenAPI specification at the navigation level. This enables automatic endpoint inclusion throughout your documentation:
-
-```json {3, 13-14}
-{
-  "navigation": {
-    "openapi": "/path/to/openapi.json",
-    "tabs": [
-      {
-        "tab": "Getting started",
-        "pages": ["quickstart", "installation"]
-      },
-      {
-        "tab": "API reference",
-        "pages": [
-          "api-overview",
-          "GET /users",
-          "POST /users",
-          "guides/authentication"
-        ]
-      }
-    ]
-  }
-}
-```
-
-Any page entry matching the format `METHOD /path` will generate an API page for that endpoint using the default OpenAPI spec.
-
-#### OpenAPI spec inheritance
-
-OpenAPI specifications are inherited down the navigation hierarchy. Child navigation elements inherit their parent's OpenAPI specification unless they define their own:
-
-```json {3, 10-11, 16, 18-19}
-{
-  "navigation": {
-    "openapi": "/path/to/openapi-v1.json",
-    "tabs": [
-      {
-        "tab": "API v1 reference",
-        "pages": [
-          "overview",
-          "authentication",
-          "GET /users",
-          "POST /users"
-        ]
-      },
-      {
-        "tab": "API v2 reference",
-        "openapi": "/path/to/openapi-v2.json", 
-        "pages": [
-          "GET /users",
-          "POST /users"
-        ]
-      }
-    ]
-  }
-}
-```
-
-#### Individual endpoints
-
-Reference specific endpoints without setting a default OpenAPI specification by including the file path:
-
-```json {6-7}
-{
-  "navigation": {
-    "pages": [
-      "introduction",
-      "user-guides",
-      "/path/to/openapi-v1.json POST /users",
-      "/path/to/openapi-v2.json GET /orders"
-    ]
-  }
-}
-```
-
-This approach is useful when you need individual endpoints from different specs or only want to include select endpoints.
-
 ## Create `MDX` files for API pages
 
-For control over individual endpoint pages, you can also create `MDX` pages for each operation. This lets you customize page metadata, add content, omit certain operations, or reorder pages in your navigation at the page level.
+For control over individual endpoint pages, create `MDX` pages for each operation. This lets you customize page metadata, add content, omit certain operations, or reorder pages in your navigation at the page level.
 
 See an [example MDX OpenAPI page from MindsDB](https://github.com/mindsdb/mindsdb/blob/main/docs/rest/databases/create-databases.mdx?plain=1) and how it appears in their [live documentation](https://docs.mindsdb.com/rest/databases/create-databases).
 

api-playground/openapi-setup.mdx

@@ -48,25 +48,6 @@ We recommend generating your API playground from an OpenAPI specification. See [
     }
     ```
 
-    To generate pages for only specific endpoints, list the endpoints in the `pages` property of the navigation element.
-
-    This example generates pages for only the `GET /users` and `POST /users` endpoints. To genereate other endpoint pages, add additional endpoints to the `pages` array.
-    
-    ```json
-    {
-        "navigation": [
-          {
-            "group": "API reference",
-            "openapi": "openapi.json",
-            "pages": [
-              "GET /users",
-              "POST /users"
-            ]
-          }
-      ]
-    }
-    ```
-
   </Step>
 </Steps>
 

api-playground/overview.mdx

@@ -71,34 +71,4 @@ If your API pages aren't displaying correctly, check these common configuration
 
     Alternatively, if your reverse proxy prevents you from accepting `POST` requests, you can configure Mintlify to send requests directly to your backend with the `api.playground.proxy` setting in the `docs.json`, as described in the [settings documentation](/settings#param-proxy). When using this configuration, you will need to configure CORS on your server since requests will come directly from users' browsers rather than through your proxy.
   </Accordion>
-  <Accordion title="OpenAPI navigation entries are not generating pages">
-    If you are using an OpenAPI navigation configuration, but the pages aren't generating, check these common issues:
-
-    1. **Missing default OpenAPI spec**: Ensure you have an `openapi` field set at the navigation level:
-       ```json
-       {
-         "navigation": {
-           "openapi": "/path/to/openapi.json",
-           "pages": ["GET /users", "POST /users"]
-         }
-       }
-       ```
-
-    2. **OpenAPI spec inheritance**: If using nested navigation, ensure child groups inherit the correct OpenAPI spec or specify their own.
-
-    3. **Validation issues**: Use `mint openapi-check <path-to-openapi-file>` to verify your OpenAPI document is valid.
-  </Accordion>
-  <Accordion title="Some OpenAPI operations appear in navigation but others don't">
-
-    1. **Hidden operations**: Operations marked with `x-hidden: true` in your OpenAPI spec won't appear in auto-generated navigation.
-    2. **Invalid operations**: Operations with validation errors in the OpenAPI spec may be skipped. Check your OpenAPI document for syntax errors.
-    3. **Manual vs automatic inclusion**: If you reference any endpoints from an OpenAPI spec, only the explicitly referenced operations will appear in navigation. No other pages will be automatically added. This includes operations that are referenced in child navigation elements.
-  </Accordion>
-  <Accordion title="Mixed navigation (OpenAPI and MDX pages) not working correctly">
-    When combining OpenAPI operations with regular documentation pages in navigation:
-
-    1. **File conflicts**: You cannot have both an `MDX` file and a navigation entry for the same operation. For example, if you have `get-users.mdx`, do not also include `"GET /users"` in your navigation.  If you need to have a file that shares a name with an operation, use the `x-mint` extension for the endpoint to have the href point to a different location.
-    2. **Path resolution**: Navigation entries that don't match OpenAPI operations will be treated as file paths. Ensure your `MDX` files exist at the expected locations.
-    3. **Case sensitivity**: OpenAPI operation matching is case-sensitive. Ensure HTTP methods are uppercase in navigation entries.
-  </Accordion>
 </AccordionGroup>

api-playground/troubleshooting.mdx

@@ -81,7 +81,6 @@
             "pages": [
               "api-playground/overview",
               "api-playground/openapi-setup",
-              "api-playground/migrating-from-mdx",
               {
                 "group": "Customization",
                 "icon": "wrench",

docs.json

@@ -260,43 +260,6 @@ While not required, we also recommend that you set an icon for each dropdown ite
 
 ---
 
-## OpenAPI
-
-Integrate OpenAPI specifications directly into your navigation structure to automatically generate API documentation. Create dedicated API sections or place endpoint pages within other navigation components.
-
-Set a default OpenAPI specification at any level of your navigation hierarchy. Child elements will inherit this specification unless they define their own specification.
-
-```json
-{
-  "navigation": {
-    "openapi": "/path/to/openapi-v1.json",
-    "tabs": [
-      {
-        "tab": "API v1 reference",
-        "pages": [
-          "overview",
-          "authentication",
-          "GET /users",
-          "POST /users"
-        ]
-      },
-      {
-        "tab": "API v2 reference",
-        "openapi": "/path/to/openapi-v2.json", 
-        "pages": [
-          "GET /users",
-          "POST /users"
-        ]
-      }
-    ]
-  }
-}
-```
-
-For more information about referencing OpenAPI endpoints in your docs, see the [OpenAPI setup](/api-playground/openapi-setup).
-
----
-
 ## Versions
 
 Partition your navigation into different versions.