-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
💱 Update, modernize SDEX encyclopedia #763
Comments
Hey @JFWooten4! We did think about how smart contracts will change the liquidity on Stellar section of the docs. This is good stuff and something we need to think about. |
These redirects will need to change:
And of course you'll need to do something here. |
Hi @JFWooten4! We are going to remove some of the issues in the docs repo that are more idea-focused to make our issues a little more actionable. I'll share the spreadsheet in the comments when I have it complete so you can see our Docs Dream Journal! Going to add this issue to the spreadsheet instead of keeping it in the docs issues. |
What problem does your feature solve?
The SDEX is of growing importance to the Stellar network.
After introducing AMMs, its role became more nuanced.
With Soroban, trading has even more particulars.
What would you like to see?
There is currently only one page for all liquidity on Stellar, despite an entire encyclopedia section for the SDEX:
With the SDEX squashed together with liquidity pools (and no documentation on Soroban), it is challenging to dive into the nuances of each specific system.
Since all these relate to trading, they should probably be kept together under the SDEX directory with their own specific pages.
What alternatives are there?
We could put specific Soroban trading information under the build/smart-contracts, but this seems antithetical to startup builders' concerns.
This separation of information namely leaves new community members without a comprehensive understanding of liquidity interfaces across the newtwork.
Lastly, we could keep all trading information in one place as is in the current article, but this will not adequately adapt to ongoing SPEEDEX developments.
The text was updated successfully, but these errors were encountered: