Skip to content

Add the API hub landing page - #3404

Merged
borland merged 4 commits into
mainfrom
ellen/api-hubpage
Aug 21, 2026
Merged

Add the API hub landing page#3404
borland merged 4 commits into
mainfrom
ellen/api-hubpage

Conversation

@ellen-octopus

@ellen-octopus ellen-octopus commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Update from Orion: I rebased the PR, which picked up changes from main and rendered the below test/areas/layout changes redundant. I rolled them back and incorporated the design so we can merge it.

I removed the "Create API key" button because it didn't render properly with the layout updates, it looked weird. Easy to add later when things settle down


Changes to these pages are entirely Claude-driven, and were made in an attempt to make the checks pass validation. I suspect it's not very accurate:


Claude generated summary:

Summary

  • Adds /docs/api as a hub landing page linking to common endpoints, API client libraries, and community resources
  • Extends Api.astro and the API stylesheets to support this hub layout (no breadcrumbs/feedback widget, its own content width) separate from the generated per-endpoint reference pages
  • The API hub page's navTitle: Get started (its left-nav label) was leaking into the breadcrumb trail on every API endpoint page, e.g. Docs > Get started > Accounts instead of Docs > API > Accounts.
  • Added crumbTitle: API to the hub page's frontmatter, and removed the now-redundant sectionCrumb splice in areas.ts — that was a workaround from before the hub page existed as a real route.
  • Updated tests/api-page.spec.ts, which still pinned pre-hub-page behavior:
    • the breadcrumb crumb as unlinked text 'Api' → now a linked 'API' crumb
    • /docs/api/ expected to 404 → now 200 (it's the hub page)
    • /docs/api/index expected to 404 → now 200 (the built site serves clean URLs, so it resolves to the same file as /docs/api/)

See the new page here

Screenshot:
CleanShot 2026-08-20 at 17 28 21@2x

@ellen-octopus
ellen-octopus marked this pull request as ready for review August 20, 2026 07:29
@ellen-octopus
ellen-octopus marked this pull request as draft August 20, 2026 07:41
@ellen-octopus
ellen-octopus marked this pull request as ready for review August 20, 2026 08:37
@ellen-octopus
ellen-octopus marked this pull request as draft August 20, 2026 08:37
@team-marketing-branch-protections

Copy link
Copy Markdown

Pull request environment is available at https://stoctodocspr3404.z22.web.core.windows.net.

You can view the ephemeral environment status in Octopus Deploy.

This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity.

ellen-octopus and others added 4 commits August 21, 2026 17:18
Introduces /docs/api as a hub page linking to common endpoints, client
libraries, and community resources, distinct from the generated
per-endpoint reference pages. Api.astro and the API stylesheets gain
support for this hub layout (no breadcrumbs/feedback widget, its own
content width).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

# Conflicts:
#	src/layouts/Api.astro
The API hub page's navTitle ("Get started", used for its left-nav
label) was being reused as its breadcrumb crumb on every child page.
Give it a distinct crumbTitle and drop the now-redundant sectionCrumb
splice, since the hub page is a real route the breadcrumb walk finds
on its own.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@borland
borland force-pushed the ellen/api-hubpage branch from 790209b to 59d203f Compare August 21, 2026 05:32
@borland
borland marked this pull request as ready for review August 21, 2026 05:33
@borland
borland enabled auto-merge (squash) August 21, 2026 05:34
@borland
borland merged commit 83cd06b into main Aug 21, 2026
7 checks passed
@borland
borland deleted the ellen/api-hubpage branch August 21, 2026 05:44
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.

3 participants