Task based IA

ai-native.mdx

@@ -0,0 +1,45 @@
+---
+title: "AI-native docs"
+description: "Learn how AI enhances reading, writing, and distributing your docs"
+icon: "cpu"
+---
+
+When you host your documentation on Mintlify, built-in AI features help your users find answers and your team maintain content more efficiently. These AI-native features analyze your docs to improve the experience of reading, writing, and distributing your docs.
+
+## What makes your docs AI-native
+
+### Content suggestions
+Users can chat with the assistant to get answers and links to relevant pages to guide them through using your product. Embed the assistant into custom apps with the [API](api-reference/assistant/create-assistant-message).
+
+If a user encounters a 404 error, your site suggests related pages to help them find what they're looking for. No configuration required.
+
+### Search-optimized
+Mintlify automatically hosts `llms.txt` and `llms-full.txt` files for your docs. These files are an industry standard that help LLMs index content. AI tools use these files to process the structure of your documentation and find content relevant to user queries.
+
+Mintlify also hosts an MCP server for your docs site that lets users connect your docs directly to their AI tools so that they have up to date information about your product directly where they want it.
+
+Full-text search and semantic understanding help users and AI tools find relevant information quickly. Search on your docs understands user intent rather than just matching keywords.
+
+### Structured content
+Your MDX pages generate semantic HTML with proper heading hierarchies, which makes it easy for AI tools to understand and reference your content. Every page is available as Markdown by appending `.md` to the page's URL.
+
+Page frontmatter—like titles, descriptions, and tags—provides context that helps AI tools understand the purpose and scope of each page.
+
+## Enable additional AI features
+
+Select any of the following cards for more information.
+
+<CardGroup cols={2}>
+  <Card title="Assistant" icon="bot-message-square" href="/guides/assistant">
+    Configure the assistant to search external sites or direct people to your support team if it can't answer their questions.
+  </Card>
+  <Card title="Contextual menu" icon="sparkles" href="/ai/contextual-menu">
+    Add a menu to pages that lets users query AI tools, connect to your MCP server, and copy pages as context with one click.
+  </Card>
+  <Card title="MCP integration" icon="plug" href="/ai/model-context-protocol">
+    Your site has a hosted MCP server that lets users connect your docs directly to their AI tools. Make your users aware of your MCP server and how to connect to it.
+  </Card>
+  <Card title="Editor integrations" icon="code">
+    Configure [Claude Code](/guides/claude-code), [Cursor](/guides/cursor), or [Windsurf](/guides/windsurf) to help write, review and update your docs.
+  </Card>
+</CardGroup>

api-playground/migrating-from-mdx.mdx

@@ -2,14 +2,13 @@
 title: "Migrating MDX API pages to OpenAPI navigation"
 sidebarTitle: "Migrating from MDX"
 description: "Update from individual MDX endpoint pages to automated OpenAPI generation with flexible navigation"
-icon: "arrow-big-right-dash"
 ---
 
 If you are currently using individual `MDX` pages for your API endpoints, you can migrate to autogenerating pages from your OpenAPI specification while retaining the customizability of individual pages. This can help you reduce the number of files you need to maintain and improve the consistency of your API documentation.
 
 You can define metadata and content for each endpoint in your OpenAPI specification and organize endpoints where you want them in your navigation.
 
 ## CLI migration
 
 The `mint migrate-mdx` command is the recommended way to migrate from MDX endpoint pages to autogenerated pages.
 
@@ -21,11 +20,11 @@
 - Deletes the original MDX endpoint files.
 
 <Info>
 If you already have `x-mint` defined for an endpoint and also have an MDX page with content for that endpoint, the MDX content will overwrite existing `x-mint` settings.
 
 If you have multiple MDX pages for the same endpoint with different content, the script will use the content from the page that appears last in your `docs.json`.
 
 The migration tool does not support previewing changes before applying them.
 </Info>
 
 <Steps>
@@ -39,7 +38,7 @@
     </Tip>
   </Step>
   <Step title="Install the Mint CLI">
     If needed, install or update the [Mint CLI](/installation).
   </Step>
   <Step title="Run the migration command.">
     ```bash