Skip to content

docs: improve IA for automation developers — surface Quick Start Guide#9

Open
ekline[bot] wants to merge 2 commits into
mainfrom
docs/persona-ia-review-2026-03-23
Open

docs: improve IA for automation developers — surface Quick Start Guide#9
ekline[bot] wants to merge 2 commits into
mainfrom
docs/persona-ia-review-2026-03-23

Conversation

@ekline

@ekline ekline Bot commented Mar 23, 2026

Copy link
Copy Markdown
Contributor

Persona context

This PR addresses findings from a persona-scoped information architecture review of the Fastn documentation. Three personas were evaluated:

  • Automation Developer (beginner-intermediate) — wants to build their first flow
  • AI Developer (intermediate-advanced) — wants to connect AI agents via UCL/MCP
  • SaaS Product Builder (intermediate) — wants to embed Fastn integrations into their product

Top 3 findings

Rank Priority Persona Issue Affected area Proposed fix
1 High Automation Developer Quick Start Guide buried below 40+ reference pages in sidebar; "Your First Automation" onboarding page links only to UCL tutorials, not the Quick Start SUMMARY.md, your-first-automation.md Move Quick Start to top of Flows section; add prominent link from onboarding page
2 High AI Developer "Embedding UCL onto your AI Agent" nested 3 levels deep under conceptual-sounding "About Unified Context Layer" SUMMARY.md, UCL Getting Started page Promote embedding guide to top-level UCL item; add callout on landing page
3 Medium SaaS Product Builder Embedded Integrations and Flows sections are completely siloed with zero cross-links embedded-integrations/README.md Add cross-links between Embedded Integrations and Flows

What this PR fixes

Finding #1 — Quick Start Guide discoverability (Automation Developer)

  • SUMMARY.md: Moved "Quick Start Guide" from below "Flow Setup Essentials" (position 75 in sidebar) to the first item under the Flows section
  • your-first-automation.md: Restructured the onboarding page into three clear paths with the Quick Start Guide as the most prominent entry point

Finding #2 — UCL embedding guide visibility (AI Developer)

  • SUMMARY.md: Promoted "Embedding UCL onto your AI Agent" from 3 levels deep (under "About Unified Context Layer") to a direct child of "Getting Started" — now the first item AI developers see when they expand the UCL section
  • ucl-unified-context-layer/getting-started/README.md: Added a prominent success callout at the top of the UCL landing page linking directly to the embedding guide

Remaining items (follow-up work)

How to verify

  1. Preview the GitBook site with these changes
  2. Finding Small update to the Information Architecture. #1: Navigate to Getting Started → Your First Automation — confirm the Quick Start Guide link is the first and most prominent option. Expand Flows in the sidebar — confirm "Quick Start Guide" appears first.
  3. Finding Tutorial: Your first embedded integration widget #2: Expand AI agent integrations (UCL) → Getting Started in the sidebar — confirm "Embedding UCL onto your AI Agent" appears as the first child item, before "About Unified Context Layer". Open the UCL Getting Started page — confirm the green callout links to the embedding guide.
  4. Verify all existing sidebar links still resolve correctly

ekline Bot added 2 commits March 23, 2026 19:05
…m onboarding page

The Flows Quick Start Guide was buried below 40+ reference pages in the
sidebar, making it invisible to new users. The main onboarding page
("Your First Automation") linked only to UCL tutorials, not the Quick
Start. This reorders the sidebar and adds a prominent Quick Start link
on the onboarding page so automation developers find the starting point
immediately.
…velopers

"Embedding UCL onto your AI Agent" was nested 3 levels deep under the
conceptual "About Unified Context Layer" section. AI developers looking
for implementation steps had to click through conceptual content first.

This promotes the embedding guide to sit directly under "Getting Started"
in the UCL section, and adds a prominent callout on the UCL landing page
linking to it.
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.

0 participants