Documentation Restructure: Four Tabs, Split by Audience

The docs were organised by protocol and category, which meant a how-to and the reference it pointed to could sit in different parts of the tree.

docs.stackone.com now splits at the top level by whether the reader is writing code. Work done in the dashboard sits under Gateway; work done in an editor sits under Embed. Four tabs replace the folder tree, and each is an ordered path where every page links to the next step.

What’s new

• Gateway - the no-code path through the dashboard. Introduction, Connect, Optimize and Secure run in order, from core concepts through linking a connector to the governance answers needed before sign-off.
• Connectors - the generated per-provider catalogue, 1,695 pages of it, plus Connector Building for the build workflow, defined output schemas, events, GitHub CI/CD and the YAML reference.
• Embed - the developer journey walked once, end to end: authentication, connect session, account linking, Call Actions, account events. Shared content is single-sourced through snippets, so the same instruction no longer appears three times at three levels of staleness.
• Platform API - a narrative overview in front of the generated reference for Accounts, Actions, Connect Sessions, Connector Profiles, MCP and Logs.
• Agent Setup for ten clients - new pages for ChatGPT, Codex, Cursor, VS Code and Gemini; rewritten pages for Claude Desktop, Claude Code, Goose, n8n and Flowise. Each page covers one client end to end, from connecting StackOne to the first tool call.
• Call Actions is the one place protocols live - a page each for the Agent SDK, MCP, A2A and RPC/HTTP, at the point in the journey where you choose between them. Framework guides for OpenAI, Vercel, LangChain, LangGraph, CrewAI and Pydantic AI nest under Agent SDK.
• Every page is also markdown - add .md to any docs URL to get the raw source, and llms-full.txt reflects the new structure. Each page carries copy, view-as-markdown, and open-in ChatGPT / Claude / Perplexity actions.
• Terminology fixed at the source - a Connector Profile is a Connector Profile on every maintained page, and StackOne Hub is StackOne Hub. The old “Auth Config” and “Integration Hub” names are gone.

Why this shape

Docs are increasingly read by agents as well as by people, and both navigate the same way: they land on a page and look for the next step. One ordered path serves both, so there is a single set of pages to maintain rather than a human version and an agent version alongside it.

Start at docs.stackone.com.