Skip to content

Conversation

@nearestnabors
Copy link
Contributor

@nearestnabors nearestnabors commented Dec 30, 2025

  • Moves docs to new IA structure
  • Removes top nav
  • Updates internal links to new URLs
  • Adds permanent redirects to new URLs

Preview

Screenshot 2025-12-30 at 10 59 04 PM

Note

Implements a major documentation IA overhaul with new top-level sections and extensive path/link updates.

  • Introduces new structure: app/en/get-started, app/en/guides, app/en/references, app/en/resources; adds many corresponding _meta.tsx files and pages; removes legacy home metas/pages
  • Updates internal links across numerous guides (agent frameworks, tool-calling, create-tools, deployment-hosting, security, auth providers) to new routes; adjusts titles and copy where needed
  • Component tweaks: comments out Badge in Logo, updates ToolInfo/StarterToolInfo link targets, changes editPage label text
  • Workflow/script updates: translate workflow help text path, trim whitespace, and switch example-date script path to new resources/examples
  • Potential impact: widespread route changes (redirects not included), risk of broken links and downstream importer path assumptions (e.g., translation, example updater)

Written by Cursor Bugbot for commit d9c3dab. This will update automatically on new commits. Configure here.

@vercel
Copy link

vercel bot commented Dec 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs Ready Ready Preview, Comment Dec 30, 2025 10:50pm

- Migrated 176 files with 2,657 link updates total
- Updated links from /home/ paths to new structure:
  - /get-started/ for onboarding content
  - /guides/ for how-to guides
  - /references/ for reference documentation
  - /resources/ for supplementary content
- Based on URL mappings from docs-migration.csv

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
nearestnabors and others added 2 commits December 30, 2025 21:49
- Added 61 permanent (308) redirects in next.config.ts
- Maps old /home/ paths to new information architecture
- Uses Next.js redirects() for server-side handling
- SEO-friendly: search engines will update their indexes

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
- Updated 119 files with remaining /home/ references
- Fixed links with anchors and query parameters
- Ensured all internal links point to new IA structure
- Comprehensive mapping of all /home/ paths to new locations

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
## Next Steps

- Learn more about [MCP Gateways](/home/mcp-gateways).
- Learn more about [MCP Gateways](/guides/create-tools/mcp-gateways.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing closing parentheses break multiple markdown links

Several markdown links are missing their closing ), breaking the link syntax. For example, [MCP Gateways](/guides/create-tools/mcp-gateways. is missing the closing parenthesis. This affects multiple files including call-tool-client/page.mdx, arcade-deploy/page.mdx, cursor/page.mdx, visual-studio-code/page.mdx, and securing-arcade-mcp/page.mdx. These broken links will render incorrectly and fail to navigate users to the intended destinations.

Additional Locations (2)

Fix in Cursor Fix in Web

Arcade Deploy](/home/serve-tools/arcade-deploy) guide or the [on-prem MCP
server](/home/deployment/on-prem-mcp) guide for secure remote deployment.
Arcade Deploy](/guides/deployment-hosting/arcade-deploy) guide or the [on-prem MCP
server](/guides/deployment-hosting/on-prem guide for secure remote deployment.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing closing parenthesis in on-prem documentation links

Links to the on-prem deployment guide are malformed with missing closing parentheses: /guides/deployment-hosting/on-prem guide instead of /guides/deployment-hosting/on-prem). This occurs in multiple documentation files including mcp-server-quickstart/page.mdx, build-mcp-server/page.mdx, call-tools-mcp/page.mdx, create-tool-secrets/page.mdx, and deployment-hosting/page.mdx.

Additional Locations (2)

Fix in Cursor Fix in Web

| http | local ([unprotected](/resources/glossaryunprotected-mcp-servers)) |||||
| http | remote ([unprotected](/resources/glossaryunprotected-mcp-servers)) |||||
| http | local ([protected](/resources/glossaryprotected-mcp-servers)) `coming soon` |||||
| http | remote ([protected](/resources/glossaryprotected-mcp-servers)) |||||
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glossary anchor links missing hash symbol

The glossary links are missing the # hash separator between the path and anchor. For example, /resources/glossaryunprotected-mcp-servers should be /resources/glossary#unprotected-mcp-servers. All four glossary links in the table are affected, which will result in 404 errors instead of navigating to the correct glossary sections.

Fix in Cursor Fix in Web

## Next Steps

In this simple example, we call the tool methods directly. In your real applications and agents, you'll likely be letting the LLM decide which tools to call. Learn more about using Arcade with Frameworks in the [Frameworks](/home/langchain/use-arcade-tools) section, or [how to build your own tools](/home/build-tools/create-a-mcp-server).
In this simple example, we call the tool methods directly. In your real applications and agents, you'll likely be letting the LLM decide which tools to call. Learn more about using Arcade with Frameworks in the [Frameworks](/guides/agent-frameworks/langchain/python section, or [how to build your own tools](/guides/create-tools/tool-basics/build-mcp-server).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Broken link missing closing parenthesis in agent guide

The markdown link [Frameworks](/guides/agent-frameworks/langchain/python section, is malformed - it's missing the closing ) before the comma and also has the word "section" incorrectly placed inside the URL. This breaks both the link syntax and will cause rendering issues.

Fix in Cursor Fix in Web

* [Visual Studio Code](/home/mcp-clients/visual-studio-code)
* [Cursor](/guides/tool-calling/mcp-client/visual-studio-code)
* [Claude Desktop](/guides/tool-calling/mcp-client/visual-studio-code)
* [Visual Studio Code](/guides/tool-calling/mcp-client/visual-studio-code)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MCP client links all point to VS Code page

All three MCP client links (Cursor, Claude Desktop, and Visual Studio Code) incorrectly point to the same /guides/tool-calling/mcp-client/visual-studio-code path. Cursor and Claude Desktop should link to their respective documentation pages, not the VS Code page.

Fix in Cursor Fix in Web

- Learn how to [use Arcade tools](/home/mastra/use-arcade-tools) in a Mastra agent
- Implement [user authentication handling](/home/mastra/user-auth-interrupts) for tools in multi-user applications
- Learn how to [use Arcade tools](/resources/mastra/use-arcade-tools) in a Mastra agent
- Implement [user authentication handling](/resources/mastra/user-auth-interrupts) for tools in multi-user applications
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect paths reference non-existent /resources/ routes

Links in the Mastra and OpenAI Agents documentation incorrectly point to /resources/mastra/ and /resources/oai-agents/ paths, but the actual files are located under /guides/agent-frameworks/mastra/ and /guides/agent-frameworks/openai-agents/. These links will result in 404 errors.

Additional Locations (1)

Fix in Cursor Fix in Web

## Quick Comparison

| Aspect | [Resource Server Auth (Front-Door)](/home/build-tools/secure-your-mcp-server) | [Tool-Level Authorization](/home/build-tools/create-a-tool-with-auth) |
| Aspect | [Resource Server Auth (Front-Door)](/guides/security/secure-your-mcp-server | [Tool-Level Authorization](/guides/create-tools/tool-basics/create-tool-auth) |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing closing parenthesis in table header link

The markdown table header contains a broken link: [Resource Server Auth (Front-Door)](/guides/security/secure-your-mcp-server | is missing the closing ) before the pipe character. This will cause the table rendering to break and the link to be non-functional.

Fix in Cursor Fix in Web


- [Using Arcade tools](/home/google-adk/use-arcade-tools) - Learn the basics of using Arcade tools with Google ADK
- [Creating custom tools](/home/build-tools/create-a-mcp-server) - Build your own tools with the Arcade Tool SDK
- [Using Arcade tools](/guides/agent-frameworks/google-adk/python) - Learn the basics of using Arcade tools with Google ADK
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect path uses /python instead of /use-arcade-tools

The link [Using Arcade tools](/guides/agent-frameworks/google-adk/python) points to a non-existent /python path. Based on the file structure in the _meta.tsx, the correct path should be /guides/agent-frameworks/google-adk/use-arcade-tools to match the actual documentation page.

Fix in Cursor Fix in Web

OAuth app credentials and add them to Arcade. For example, see our docs on
[configuring Google auth in the Arcade
Dashboard](/home/auth-providers/google#access-the-arcade-dashboard).
Dashboard](/references/auth-providers/googleaccess-the-arcade-dashboard).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing hash symbol in Google auth provider anchor link

The link /references/auth-providers/googleaccess-the-arcade-dashboard is missing the # hash symbol between the path and anchor. It should be /references/auth-providers/google#access-the-arcade-dashboard. This will result in a 404 instead of navigating to the correct section.

Fix in Cursor Fix in Web

@EricGustin
Copy link
Member

EricGustin commented Dec 31, 2025

For some reason the integrations aren't being listed alphabetically within their respective category.
Screenshot 2025-12-31 at 10 17 50 AM

Additional thoughts (feel free to ignore):

  • I'd like to challenge the organizing of integrations into categories like "Productivity & Docs", "Entertainment", etc. This organization structure existed before this PR, but IMO, the categories are too subjective & makes discovery more difficult than if we just listed integrations alphabetically without the categories.

Copy link
Contributor

@evantahler evantahler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a review based on the preview site holistically - I haven't reviewed the code. If you would like a code review, @ me on a page and I can take a look!

In general, I like the new IA - I like both the high level categories, and how the user works down form intro to advanced topics as they go.

Some blocking items:

  • The sidebar links in the "references" section do not work (either 404 or 'too many redirects'), except for 'auth providers'
  • Navigationally, the list of integrations/toolkits moving under 'resources' is fine, but this page is really important for the "should I use Arcade" decision making process. I think that means is should have a top-nav link as well. It should also be called out in some way to differentiate the importance of that page.
  • I agree with @EricGustin that the tool-type categorization (productivity, sales, etc) probably matters less than the list of APIs we we support. A categorization I do think matters now is "starter" vs "optimized". We should focus on the starter tools and de-emphasize the starter tools - they are mixed now.
  • 'Submit your Server' doesn't do anything

Questions I have:

  • The new 'about arcade' is good! How does that relate to the 'home' page - can they be merged or are they doing different jobs?

@evantahler
Copy link
Contributor

One more nit - the get-started/quickstarts/call-tool-agent page doesn't actually teach you how to use Arcade in an agent - it teaches you how to use Arcade's tool programmatically, like any old function. I think either the title is misleading, or the tutorial should end with the use of the smallest agent framework available (e.g. OpenAI AgentsSDK?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants