> ## Documentation Index > Fetch the complete documentation index at: https://anvil.servicetitan.com/llms.txt > Use this file to discover all available pages before exploring further. # What's changing in Anvil2 docs October 16, 2026 | ## Where we've been To date, the Anvil2 documentation has been difficult to navigate as a consequence of reflecting how the system grew: web was the long-established and de facto center; React Native and mobile platforms arrived through distinct efforts; disparate 'Design' and 'Code' pages served different working contexts; Carto/AI Kit had its own identity while agentic work was emerging; and so on. Over time, the information architecture grew to imply that Anvil2 is a disjointed collection of libraries, rather than a cohesive system that works across platforms. So why the change? We want to make it clear: **Anvil2 is one design system expressed across platforms and product contexts.** ## One design system With sustained growth in mobile platforms and agentic experiences, we're committed, as always, to enabling teams to build great products. To do that, we needed to realign and strengthen our documentation. With 'one design system' as our guiding principle, we've updated the documentation to reflect the following goals: 1. **Every platform is an equal partner.** Web, React Native, iOS, and Android all sit on equal footing under Anvil2. A component or pattern is the primary idea; platform is a dimension of its implementation. 2. **Agentic experiences are an integral part of Anvil2.** What we've previously documented distinctly as Carto/AI Kit is now documented in-line with the rest of Anvil2. This makes it clear: Agentic is deeply engrained inside the system's normal vocabulary. 3. **The docs work equally well for people and for agents.** We've consolidated much of our documentation to speak with greater consistency. Designers, engineers, PMs, and AI tools should encounter the same underlying account of a thing, even when they need different details. Docs
    All Anvil2 documentation has been consolidated into three groups: Concepts & Guidelines, Anvil2, and Resources. ### Every platform is an equal partner Web, React Native, iOS, and Android are peer platforms. Our documentation has historically emphasized web-specific documentation, but as we continue to make product investments on mobile, we're ensuring that our documentation reflects that every platform is an equal partner. Putting platform pages under one component/pattern page makes differences visible and invites teams to ask whether they are intentional. We believe that documenting in this cross-platform way will not just record consistency, but help to create it. Button One component, one page per platform. * **Components and patterns come first, platforms second.** Each component or pattern has one page per platform, for example `Button - Web` or `Action Log - React Native`. You start from the thing you're building, then pick your platform. This choice was made to help drive closer alignment between components across platforms. * **New platforms extend the existing structure.** As iOS and Android components ship, they become another platform page under the same component, not a new top-level section. * **Getting Started includes a foothold for each platform.** [Web](https://anvil.servicetitan.com/docs/getting-started/web.md), [React Native](https://anvil.servicetitan.com/docs/getting-started/react-native.md), [iOS](https://anvil.servicetitan.com/docs/getting-started/ios.md), and [Android](https://anvil.servicetitan.com/docs/getting-started/android.md). * **Supporting library docs are updated to cover previously undocumented platforms.** [Charts](https://anvil.servicetitan.com/docs/charts) has Web and React Native sections side by side. [Icons](https://anvil.servicetitan.com/docs/icons), [Illustrations](https://anvil.servicetitan.com/docs/illustrations), and [Design Tokens](https://anvil.servicetitan.com/docs/design-tokens.md) each have one home under Anvil2 instead of hanging off the Web tree. ### Agentic experiences are an integral part of Anvil2 Building agentic experiences is a core function of Anvil2 going forward, so it no longer lives in a separate kit. Carto is the Anvil2 theme that powers these experiences (see [Explaining Carto, a new Anvil2 theme](https://anvil.servicetitan.com/blog/posts/2026-09-14-explaining-carto-a-new-anvil2-theme.md)), and AI Kit components are now documented as Anvil2 components. * **Kits are no longer a separate destination.** AI Kit components appear in the main [Components](https://anvil.servicetitan.com/docs/components.md) list alongside every other Anvil2 component. Agentic components like Agent Message, Agent Thinking, and Chat Layout sit next to Button and Dialog. * **Same-named components share one entry.** When AI Kit ships a component with the same name as a core component, such as Button or Dialog, its page appears under that component as **Web (AI Kit)**. It is not a second top-level entry. * **Agentic guidance lives with the rest of our guidance.** [Building Agentic Experiences](https://anvil.servicetitan.com/docs/building-agentic-experiences) sits under Concepts & Guidelines with Design Foundations and Content. It covers AI UX, visual foundations, voice, chat, and tone and trust. * **One voice.** Agentic components and guidance follow the same page structure, titles, and writing standards as the rest of Anvil2. Old AI Kit URLs redirect to their new locations. ### The docs work equally well for people and for agents People and AI tools read the same pages, so the structure has to serve both equally. Additionally, we've consolidated much of our component documentation to speak consistently to designers, engineers, and PMs alike. Humans Button - Web Agents Humans and agents read the same page. MCP, Claude, Cursor, and VS Code connect from that page. * **One answer per question.** Each topic has one owning page. Duplicate Design and Code routes, kit-specific copies, and parallel trees of information are gone, so neither a person nor an agent has to choose between two versions of the truth. * **Scoped, predictable pages.** Platform pages keep implementation detail scoped to a single platform, and titles follow one `{thing} - {platform}` format. That makes pages easier to scan for people and easier to retrieve accurately for agents. * **Tooling connects directly to the docs.** Every page offers options to connect the docs to MCP, Claude, Cursor, or VS Code, or to view the page as Markdown. [AI Tooling](https://anvil.servicetitan.com/docs/getting-started/ai-tooling-and-anvil2.md) now sits under Getting Started and covers how to connect the Anvil2 MCP server to your tools. * **Authoring guidance matches the new structure.** The rules that guide people and agents writing Anvil2 docs describe this structure, so our documentation stays in directional alignment going forward. ### Other enhancements and changes * **A clearer navigation order.** The Docs tab now has three groups, in a fixed order: Concepts & Guidelines, Anvil2, and Resources. * **Redirects have been configured to help smooth the transition.** Relatively few historical links or bookmarks should break. * **A Community Extensions section has been added.** This new section houses contributed extensions to Anvil2 that are not part of the core Anvil2 product. ## What's coming in Q4? While we now feel good about *where* information lives, there are still some opportunities for us to improve *what* the information actually says. A few things are top of mind for us as we go into Q4: * **Mobile documentation.** We've built the structure for stronger cross-platform documentation, we'll be adding much more content to speak to recent mobile design and development efforts. * **AI UX patterns.** We have a ton of AI UX patterns also coming that will add to and clarify the Building Agentic Experiences section. * **Further reconciliation and cleanup.** We'll be tidying up conflicting/out-of-date guidance related to AI Kit/Carto, tokens, and other areas. If you have feedback or ideas for improvement, chat with us in [#ask-designsystem](https://servicetitan.enterprise.slack.com/archives/CBSRGHTRS). ## Connect with us > **[Get help on Slack](https://servicetitan.enterprise.slack.com/archives/CBSRGHTRS)** > > You can reach the Anvil team in the #ask-designsystem Slack channel. > **[Schedule office hours](https://servicetitan.enterprise.slack.com/archives/CBSRGHTRS)** > > Join the Anvil team for office hours on Mondays or Wednesdays to get hands-on help. > **[Report an issue](https://servicetitan.atlassian.net/secure/CreateIssue.jspa?issuetype=1\&pid=11329)** > > Ran into a bug in the code or design? We use Jira to track outstanding > issues with Anvil. > **[Suggest an idea](https://slack.com/shortcuts/Ft07EXNJSPS7/f598de9eda7177f477aaddbbc5701e15)** > > Have an idea for a component, pattern, or documentation? Fill out the Feature Request Form in Slack. > **[View roadmap](https://anvil.servicetitan.com/docs/resources/roadmap.md)** > > View what is coming up this year for the design system. > **[Contribute to Anvil2](https://servicetitan.atlassian.net/wiki/spaces/ADS/pages/2054129026/Designer+Contribution+to+Anvil)** > > Interested in contributing to Anvil? Read our contribution guide to learn > more! This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.