Skip to content

docs: one sidebar entry, one page for the hosted tools - #9

Merged
jaykomarraju merged 1 commit into
mainfrom
docs/tools-one-page
Aug 16, 2026
Merged

docs: one sidebar entry, one page for the hosted tools#9
jaykomarraju merged 1 commit into
mainfrom
docs/tools-one-page

Conversation

@jaykomarraju

Copy link
Copy Markdown
Contributor

Replaces the five-item sidebar group and the home-page section with a single entrytools.tx402.io — pointing at one page that explains every tool and links to it.

The group was the wrong shape: five links to another origin sat at the same level as Guides and Reference, competing with the SDK navigation rather than sitting beside it, and still said nothing about what any of them did. A reader scanning a sidebar wants one door, not six.

The new /tools/ page carries all six tools with the question each answers, the curl that returns the same result as JSON, and links back into the guides they relate to — history → recipient-rotation, playground → policy, replay → the error taxonomy. It also states what a LOW/MEDIUM/HIGH band means, since a page listing a service that produces bands should not leave that to be inferred.

The home page keeps one line under Where to go next. It is template: splash, so the sidebar does not render there at all.

The in-page asides on the six SDK pages are untouched — they catch a reader already in a guide with the question; this catches the one who is looking.

Verified pnpm docs:build: 25 pages, 49 md mirrors.

Replaces the five-item sidebar group and the home-page section with a
single entry — tools.tx402.io — pointing at one page that explains every
tool and links to it.

The group was the wrong shape. Five links to another origin sat at the
same level as Guides and Reference and competed with the SDK navigation
rather than sitting beside it, and it still said nothing about what any
of them did. A reader scanning a sidebar wants one door, not six.

The new page carries all six tools with the question each answers, the
curl that returns the same result as JSON, and links back into the
guides they relate to — routing to recipient-rotation from history, to
policy from the playground, to the error taxonomy from replay. It also
states what a LOW/MEDIUM/HIGH band means, because a page that lists a
service producing bands should not leave that to be inferred.

The home page keeps one line under Where to go next. It is template:
splash, so the sidebar does not render there at all, and that line is
the only route from the page a first-time reader lands on.

The in-page asides on the six SDK pages are untouched. They catch a
reader who is already in a guide with the question; this catches the one
who is looking.
@jaykomarraju
jaykomarraju merged commit 0871e86 into main Aug 16, 2026
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.

1 participant