Add RWA docs tab: introduction, quickstart, and dashboard opt-in guide - #283
Draft
jlin27 wants to merge 2 commits into
Draft
Add RWA docs tab: introduction, quickstart, and dashboard opt-in guide#283jlin27 wants to merge 2 commits into
jlin27 wants to merge 2 commits into
Conversation
Documents how a team enables tokenized real-world asset (RWA) trading from the 0x Dashboard: the skippable step at signup, the RWA tab for existing teams, and what happens on acceptance (acceptance record and trading permission written together, gateway re-provisioned, access live immediately with no key rotation). The page is hidden in docs.yml and the matching FAQ entries are commented out, since the feature has not shipped and the agreement text and any additional fields are still pending legal review. Remaining unknowns are marked with TODO(pre-launch) comments.
|
🌿 Preview your docs: https://0x-preview-db001e98-fd1b-47d0-83fe-f8422641b2d5.docs.buildwithfern.com Here are the markdown pages you've updated: |
Promotes RWA from a single page under Introduction to its own tab, alongside EVM, SVM, and Cross-Chain: - Introduction to RWAs — asset categories, why RWAs route differently (blocked by default, thinner liquidity leaning on RFQ, jurisdiction dependence), and how 0x indexes and routes them. Sourced from 0x.org/solution/rwas. - RWA Quickstart — first RWA trade end to end with Swap API, covering the opt-in prerequisite, indicative price, firm quote, allowance, and submission. - Enable RWA Trading — moved from introduction/rwa-access.mdx, relinked to its siblings. The tab carries hidden: true, so nothing publishes until the feature ships. FAQ entries stay commented out and now point at the new paths.
jlin27
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drafts user-facing docs for the RWA self-serve opt-in, per the request in this Slack thread. Tracked in DEVREL-35.
This is a draft and must not merge before the feature ships and legal signs off on the agreement text.
Changes
fern/docs/pages/introduction/rwa-access.mdx— "Enable RWA Trading". Covers the skippable RWA step at signup, opting in later from the RWA tab, and what happens on acceptance.fern/docs.yml— adds the page to the Introduction section after "Supported Chains and Providers", withhidden: true.fern/docs/pages/introduction/faq.mdx— two RWA entries in the existing "0x Dashboard" section, commented out.Why a guide rather than only an FAQ
The ask was for "an FAQ or something." Opting in is a multi-step flow with a legal agreement and screenshots, which does not fit inside an accordion — so this is a short standalone page under Introduction (account-level setup, next to "Create a 0x API Key"), with two FAQ accordions that point at it for people who search rather than browse.
Why nothing publishes yet
The page is hidden in nav and the FAQ entries are commented out, so merging this publishes no user-visible content. The Fern preview build still renders the page, so it can be reviewed as it will look. Unhiding is a two-line change at launch: drop
hidden: truefromdocs.ymland uncomment the FAQ block.Open items before this can ship
Each is marked inline with a
TODO(pre-launch)comment:BUY_TOKEN_NOT_AUTHORIZED_FOR_TRADE/SELL_TOKEN_NOT_AUTHORIZED_FOR_TRADE)Testing
fern checkpasses. The only reported issues are pre-existing invalid examples inopenapi.jsonandopenapi-cross-chain.json, which this PR does not touch.