OAuth 授权流程. Copy the source, paste into the official playground, done. No coordinates — every position is stated relative to something else.
node client3 "Client app"
node authz "Authorization server" below client3
node res "Resource server" below authz
node owner "Resource owner" right of authz
edge client3 -> owner "consent"
edge owner -> authz "grant"
edge authz -> client3 "code"
edge client3 -> res "access token"npx reladraw oauth-flow.reladraw -o out.svgClient app, authorization server, resource server and the resource owner, with consent, grant, code and token edges.. Use it in API docs — the four nodes are exactly the spec's four roles.
node new_id 'New label' below anchor — placement is relative, so the solver re-flows the whole diagram instantly.edge a -> b 'your label' — labels are the fastest way to carry rates, protocols or percentages.below to right of rotates a branch sideways without touching any other line.Declare each box with node, connect them with edge, and state one position per node relative to another. Paste the source from this page into the official playground and it renders immediately.
Yes — the source is free to copy, modify and ship in docs, READMEs, books or client decks. No attribution required.
Render in the playground and export SVG, or run it locally: npx reladraw file.reladraw -o out.svg for CI-friendly builds.