Skip to content

docs(api): order client pages for first-time readers - #190

Merged
MarTrepodi merged 1 commit into
mainfrom
docs/client-page-ordering-main
Oct 14, 2026
Merged

MarTrepodi merged 1 commit into
mainfrom
docs/client-page-ordering-main

Conversation

@MarTrepodi

Copy link
Copy Markdown
Collaborator

Summary

Docs-only cherry-pick of #189 onto main, so the reordered SwgohComlink and SwgohComlinkAsync API pages publish to GitHub Pages without waiting for the next release.

Both pages now share one outline: Quick Start → Connecting to Comlink → Handling Errors → Retries and Pacing → Stat Calculation → API Reference. See #189 for the full description.

Only docs/api/comlink.md and docs/api/async.md change. The src/ code these pages document is the same as in the current release, so the generated API reference still describes released code. #189 carries the same commit into develop, so the next back-merge will not conflict.

Test plan

🤖 Generated with Claude Code

Give the SwgohComlink and SwgohComlinkAsync pages the same outline:
Quick Start, Connecting to Comlink, Handling Errors, Retries and Pacing,
Stat Calculation, API Reference.

The sync page previously opened with retry backoff details and had no
quick start; it now shows how to create, use and close a client, and how
to point it at a service and enable HMAC signing. The async page moves
error handling ahead of retries and links to the sync page for the
shared constructor and retry details.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Oct 14, 2026
@MarTrepodi
MarTrepodi merged commit b4d66ca into main Oct 14, 2026
16 checks passed
@MarTrepodi
MarTrepodi deleted the docs/client-page-ordering-main branch October 14, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant