Repository navigation
[Docs] Interactive Developer Hub, Live RPC Playground & Protocol Architecture Portal #1481
Description
Activity
@bashco-web has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Interested in working on this issue. I understand the requirements and can deliver a solution that meets the expected outcome.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @bashco-web to this issue.
@Saintricks has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi, I’d be happy to take this on. I’ve looked into the issue closely and feel confident that I can deliver a high-quality implementation quickly and efficiently.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Saintricks to this issue.
sojetunde8 commented on Sep 27, 2026
@sojetunde8 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I can fix this.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @sojetunde8 to this issue.
Congratulations, @sojetunde8! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @sojetunde8: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
This issue has been marked as completed by a Drips Wave moderator for @sojetunde8 as part of the Stellar Wave Program's 9th Wave 🥳
Moderator's reason: [Auto-assessed] The PR #1556 is merged into main (mergedAt: 2026-10-06T10:36:16Z), and issue #1481 is closed. The work comprehensively addresses the developer portal, interactive RPC playground, and architecture documentation requirements.
😎 @sojetunde8: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.
Overview & Background
As FlowFi evolves into a protocol standard on Stellar, external developers—ranging from hackathon participants to institutional integration partners—need a unified, interactive Developer Portal. Fragmented Markdown files in
docs/and raw OpenAPI YAML are insufficient. Providing a modern developer documentation site with live runnable API requests, an interactive Soroban RPC sandbox, and visual protocol sequence diagrams accelerates integration and ecosystem growth.Detailed Problem Statement
docs/,backend/docs/,packages/flowfi-sdk/).Technical Specification & Architecture
1. Developer Portal Framework (Mintlify / Docusaurus / Starlight)
Set up a dedicated documentation portal in
docs-site/or/docs:@flowfi/sdk), React (@flowfi/react), Python, Rust.2. Live Interactive RPC & Sandbox Console
create_stream,withdraw,get_stream).3. Architecture & Protocol Sequence Diagrams
Target Files
docs-site/mint.json(or Docusaurus config)docs-site/pages/quickstart.mdxdocs-site/pages/contracts/lifecycle.mdxdocs-site/pages/api-reference/.github/workflows/deploy-docs.ymlAcceptance Criteria