Skip to content

refactor: reframe introduction as the OpenAPI of UTxO#41

Merged
scarmuega merged 3 commits into
mainfrom
reframe-introduction
May 15, 2026
Merged

refactor: reframe introduction as the OpenAPI of UTxO#41
scarmuega merged 3 commits into
mainfrom
reframe-introduction

Conversation

@scarmuega
Copy link
Copy Markdown
Contributor

Summary

  • Lead index.mdx with the interface-description framing — Tx3 as the OpenAPI of UTxO — promoted from a buried single sentence to the opening paragraph.
  • Restructure the page into Two sides of the workflow / Why UTxO protocols need this / What's in the toolkit / Where the OpenAPI analogy ends / Not a smart contract language. Both CardGrids preserved verbatim.
  • Add one positioning sentence to language/index.mdx so the language guide reads as the authoring face of Tx3.

The OpenAPI analogy was already present in the previous intro, but a single buried clause; this change makes it the lead and rebuilds the surrounding sections to support it. Both sides of the workflow (authoring and consuming) are now equally visible.

Test plan

  • Build the Starlight site locally and confirm both pages render with the CardGrid and LinkCard components intact.
  • Cold-read the new opening — pretend you've never heard of Tx3 — and check that what is Tx3, who is it for, what do you do with it? is answerable in one breath.
  • Sequential re-read: index.mdxquick-start.mdxlanguage/index.mdxintegration/index.mdx. Framing should be consistent across pages.

🤖 Generated with Claude Code

scarmuega and others added 3 commits May 14, 2026 16:07
Promote the interface-description framing to the lead of the docs index
and reorganise the page into Two sides of the workflow / Why UTxO protocols
need this / What's in the toolkit / Where the OpenAPI analogy ends / Not a
smart contract language. CardGrids preserved verbatim. Also add a one-line
positioning sentence to the language guide so it reads as the authoring
face of Tx3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Remove OpenAPI from the lead sentence and delete the "Where the OpenAPI
analogy ends" section. Rewrite "Why UTxO protocols need this" so the EVM
ABI is the primary analogy and OpenAPI is mentioned as a parallel from
the web layer. Also folds in the in-flight wording tweaks to the lead and
to the Two-sides section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Lead with OpenAPI as the Web2 solution and follow with the EVM ABI as
the contract-layer solution, in two distinct paragraphs. Also replace
the misleading "format vs toolchain" lead-in to the Two-sides section
with one that names the actual contrast — author vs consumer.
@scarmuega scarmuega merged commit 2f5ac09 into main May 15, 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