Skip to content

docs: put the hosted tools in the sidebar - #7

Merged
jaykomarraju merged 1 commit into
mainfrom
docs/tools-in-sidebar
Aug 16, 2026
Merged

docs: put the hosted tools in the sidebar#7
jaykomarraju merged 1 commit into
mainfrom
docs/tools-in-sidebar

Conversation

@jaykomarraju

Copy link
Copy Markdown
Contributor

Six pages already link out to tools.tx402.io, but every one is an aside in the middle of a long page. That works for a reader already on that page with the question the tool answers. It is invisible to someone scanning the sidebar for what exists — the links were live and still could not be found, which is what prompted this.

The sidebar is autogenerated from the directory layout, so a different property cannot appear there by adding a file. This is the one place a standing entry has to be written by hand.

Five entries under Hosted tools:

Label Link
tools.tx402.io / (badged free)
Inspect an endpoint /inspect
Verify a challenge /verify
Policy playground /policy
Debug a failed payment /replay

Labelled by what they do rather than by product name, matching how the in-page asides read. Badged free because the first question about a hosted service is whether it costs anything. They open in a new tab — different origin, and losing your place in a guide to glance at a tool is a bad trade.

Verified with pnpm docs:build: 24 pages, 47 md mirrors, and all five links present in the sidebar of every built page.

Six pages already link out to tools.tx402.io, but every one of those is
an aside in the middle of a long page. That works for a reader who is
already on that page and has the question the tool answers. It is
invisible to someone scanning the sidebar to find out what exists — the
links were live and still could not be found, which is the report that
prompted this.

The sidebar is autogenerated from the directory layout, so a different
property cannot appear there by adding a file. This is the one place a
standing entry has to be written by hand.

Five links: the site itself, then the four tools a reader of these docs
is most likely to want — inspect an endpoint, verify a challenge before
signing, the policy playground, and debugging a failed payment. Labelled
by what they do rather than by product name, matching how the in-page
asides are written. Marked free, because the first question about a
hosted service is whether it costs anything.

They open in a new tab: this is a different origin, and losing your
place in a guide to look at a tool is a bad trade.
@jaykomarraju
jaykomarraju merged commit 2203065 into main Aug 16, 2026
14 checks passed
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