docs: restructure integrations sidebar with category landing pages#2643
Open
marcel-rbro wants to merge 10 commits into
Open
docs: restructure integrations sidebar with category landing pages#2643marcel-rbro wants to merge 10 commits into
marcel-rbro wants to merge 10 commits into
Conversation
Splits sources/platform/integrations/workflows-and-notifications/ and data-storage/ into purpose-built categories, adds per-provider sub-folders under ai/, and prepares a place for the upcoming HubSpot integration. Categories: - workflow-automation/ — Activepieces, IFTTT, Kestra, Make, n8n, Pipedream, viaSocket, Windmill, Workato, Zapier - ai-assistants/ — Bubble, Dify, Gumloop - collaboration/ — Drive, Gmail, Slack, Telegram - data-pipelines/ — Airbyte, Keboola, Snowflake - vector-db-storage/ — Airtable, Milvus, Pinecone, Qdrant - crm/ — placeholder for HubSpot (PR #2626) - ai/claude/ — Claude Desktop (and future Claude-specific pages) - ai/openai/ — ChatGPT, OpenAI Agents SDK, OpenAI Assistants - ai/google/ — Google ADK Each new category and provider folder has an index.mdx landing page that features S-tier integrations as cards and gives short blurbs for what each tool does with Apify. Drops tier-based sidebar_position in favor of alphabetical sidebar order. Numeric positions removed from _category_.yml files and individual pages. Renames underscored doc filenames to hyphens (integrate_with_apify.md, aws_bedrock.md, openai_agents.md, openai_assistants.md, integration_ready_actors.md, integrating_actors_via_api.md, ad_hoc_webhooks.md). Slugs left unchanged, so URLs do not break. URLs are preserved across the move; only sidebar grouping changes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
✅ Preview for this PR (commit |
Reverts the workflow-automation/ai-assistants/collaboration/data-pipelines/
vector-db-storage/crm split. Keeps the original five top-level sections
and tightens them: workflows-and-notifications/ stays as one bin, and
data-storage/ is renamed data-and-storage/ to absorb CRM-style destinations
like the upcoming HubSpot integration.
Top-level layout:
- actors/
- programming/
- ai/ (with claude/, openai/, google/ provider sub-folders)
- workflows-and-notifications/
- data-and-storage/ (was data-storage/, gains airtable and drive,
ready to host hubspot once #2626 lands)
Vector DBs (Milvus, Pinecone, Qdrant) move back to ai/ alongside the
other AI tools.
Surface entry points at the top of the integrations sidebar:
- integrate-with-apify.md sidebar_position: 1
- actors/_category_.yml position: 2
- programming/_category_.yml position: 3
AI, workflows-and-notifications, and data-and-storage sort alphabetically
after these three pinned entries.
Landing pages rewritten for the consolidated layout:
- ai/index.mdx (new): provider cards (Claude, OpenAI, Google), MCP, agent
frameworks, AI assistants, vector DBs, agent payments
- workflows-and-notifications/index.mdx (new): featured n8n/Make/Zapier/
Gumloop + full alphabetical card grid
- data-and-storage/index.mdx (rewritten): featured Snowflake/Airtable/
Keboola + full grid including Drive; HubSpot mention
- programming/index.mdx (new): API, Webhooks, GitHub cards
actors/index.md kept as-is (already a full landing page).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Main integrations page (sources/platform/integrations/index.mdx) replaces the previous Built-in / Integration platforms / AI sections with one section per sidebar category - Actors, Programming, AI, Data and storage, Workflows and notifications - each leading with that category's S-tier cards and a "see all" link. Category landing-page intros unified across the main page and the category pages so users see the same framing from either entry point. AI landing trimmed from seven sub-sections to: featured S-tier, by provider (Claude / OpenAI / Google), and a flat alphabetical "All AI integrations" grid. Adds a "Create a new integration" section to the main page explaining the page's purpose - building an integration-ready Actor or connecting a service externally via the API. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Category landing pages now show only the S-tier featured cards plus a pointer to the sidebar for the full list. The full alphabetical "All X integrations" grids on the AI, data-and-storage, and workflows-and- notifications landings are removed - the sidebar already serves that role. Drop Keboola from the data-and-storage featured grid (Mid-tier). Fetch logos for cards that were missing one: - snowflake.svg, vercel.svg + vercel-white.svg, google.svg, anthropic.svg + anthropic-white.svg from Simple Icons (CC0) - openclaw.svg from openclaw.ai - agno.png from Agno's CDN (saved for future use) Apply logos to: Snowflake, Vercel AI SDK, Google ADK, OpenClaw, Claude provider, Google provider, Claude Desktop. Logos still missing for: x402, Skyfire, Upsonic. Their sites embed logos as base64 data URIs with no fetchable file. Leaving without logos for now. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Four cards had no brand logo: Actor-to-Actor, Integration-ready Actors,
API, and x402. Use Twemoji SVGs as small visual anchors so the cards do
not look empty next to brand-logo neighbors.
- Actor-to-Actor → emoji-actor-to-actor.svg (cycle arrows)
- Integration-ready → emoji-pluggable.svg (electric plug)
- API → emoji-api.svg (gear)
- x402 → emoji-x402.svg (money with wings, for the
payments protocol)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sidebar entry "Actors" reads as ambiguous to people without deep platform context. Two changes: 1. Rename the integrations/actors/ category label from "Actors" to "Actor-to-Actor" so the sidebar tells the reader what the section is about. 2. Rewrite the actors/index.md intro to lead with what Actor-to-Actor integrations are and how they differ from third-party integrations covered elsewhere on the page. The catalog pointer moves below the intro so the framing comes first. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ixes Move agent-onboarding.md from sources/platform/integrations/ai/ to sources/platform/integrations/. Pin with sidebar_position: 2 so it sits right after "Create new integration" as the agent-builder entry point. Slug unchanged - no URL break. Bump actors/_category_.yml (3) and programming/_category_.yml (4) positions to make room. Update sidebar_label "Agent onboarding" -> "Apify for AI agents" to match the page title; the old label undersold the page's scope (MCP, Agent Skills, client libraries, REST API). Replace em-dashes with hyphen-spaces per project house style. Vale was flagging Microsoft.Dashes errors on prose introduced in this PR. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #2610. Closes #2505.
Reorganizes the integrations docs while keeping the original five top-level sections, surfaces audience-specific entry points at the top of the sidebar, and rewrites every landing page around S-tier integrations.
Five top-level sections (unchanged count)
actors/programming/ai/data-and-storage/data-storage/. Absorbs Drive + Airtable + the upcoming HubSpot integration.workflows-and-notifications/Surfaced entry points (top of the integrations sidebar)
index.mdx)integrate-with-apify.md,sidebar_position: 1) - partners building integrationsagent-onboarding.md,sidebar_position: 2) - agent builders connecting to Apify (moved up fromai/)AI provider sub-folders
Inside
ai/, three new sub-folders group provider-specific pages, each with anindex.mdxlanding page that introduces the provider and gives a short blurb on what each tool does with Apify:ai/claude/- Claude Desktop (moved fromai/mcp/)ai/openai/- ChatGPT, OpenAI Agents SDK, OpenAI Assistantsai/google/- Google ADKai/mcp/index.mdflattened toai/mcp.md(folder no longer has subpages).Sidebar sorting within sections
Tier-based
sidebar_positiondropped from every integration page. Within each category, pages sort alphabetically. Tier ranking now surfaces on landing-page card grids, not in the sidebar order.Landing pages
Every category and provider folder has an
index.mdxlanding page. Each page leads with a verbatim category blurb (reused on the main integrations page so the framing is consistent), shows the S-tier integrations as cards, and links to the sidebar for the full list. The exhaustive alphabetical grids were dropped per follow-up feedback - the sidebar already does that job.The main page (
sources/platform/integrations/index.mdx) was rewritten around the same per-category structure, plus a "Create a new integration" section explaining the partner-onboarding entry point.Logos
Fetched logos for cards that were missing one:
Filename normalization
Underscored doc filenames in
sources/platform/integrations/renamed to hyphens. Slugs left unchanged - URLs do not break.integrate_with_apify.md→integrate-with-apify.mdai/aws_bedrock.md→ai/aws-bedrock.mdai/openai_agents.md→ai/openai/openai-agents.mdai/openai_assistants.md→ai/openai/openai-assistants.mdactors/integration_ready_actors.md→actors/integration-ready-actors.mdactors/integrating_actors_via_api.md→actors/integrating-actors-via-api.mdprogramming/webhooks/ad_hoc_webhooks.md→programming/webhooks/ad-hoc-webhooks.mdURL impact
Zero. All integration pages use flat slugs (
slug: /integrations/<name>), so moves and renames do not change URLs.pnpm buildpasses (onBrokenLinks: 'throw'catches misses).Out of scope
crm/folder there and placing it directly indata-and-storage/hubspot.mdbefore merging.actors/integration-ready-actors.mdout of integrations to the Actor development section (Tomas's secondary suggestion - punted to a follow-up to keep this PR focused).Open questions
data-and-storage/rename and the inclusion of Drive + Airtable + future HubSpot./integrations/claude,/integrations/openai,/integrations/google) - any conflicts I missed?