Skip to content

[Docs] Interactive Developer Hub, Live RPC Playground & Protocol Architecture Portal #1481

Description

@blurbeast

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

  1. Scattered Documentation:
    • Architecture ADRs, threat models, backend READMEs, contract interfaces, and SDK guides are scattered across disparate directories (docs/, backend/docs/, packages/flowfi-sdk/).
  2. No Interactive API Sandbox:
    • Developers cannot test REST API endpoints, simulate transactions, or inspect webhook payloads directly within documentation.
  3. Missing Visual Sequence Diagrams:
    • Complex lifecycle flows (e.g. Batch Withdrawal, Milestone Vesting, Dead-Letter Replay, Client-Side Signing) lack interactive visual walkthroughs.

Technical Specification & Architecture

1. Developer Portal Framework (Mintlify / Docusaurus / Starlight)

Set up a dedicated documentation portal in docs-site/ or /docs:

  • Navigation Structure:
    • Getting Started: Protocol Overview, Core Concepts, Quickstart in 5 Minutes.
    • Smart Contracts: Stream Lifecycle, Storage TTLs, Batch Operations, Emergency Pause, Rust Soroban Reference.
    • Backend & Indexer: Event Ingestion, SSE/WebSocket Streams, Webhooks, Dead-Letter Triage.
    • Client SDKs: TypeScript (@flowfi/sdk), React (@flowfi/react), Python, Rust.
    • Guides & Recipes: Setting up DAO Payroll, SaaS Subscription Billing, Milestone Vesting for Grants.
    • API Reference: Interactive OpenAPI specification with "Try It Out" test console.

2. Live Interactive RPC & Sandbox Console

  • Embed an interactive Soroban RPC playground connected to Stellar Testnet:
    • Select contract method (create_stream, withdraw, get_stream).
    • Pre-filled mock parameters.
    • Real-time simulation output and decoded Soroban XDR responses.

3. Architecture & Protocol Sequence Diagrams

  • Incorporate interactive Mermaid diagrams illustrating:
    • Client-side transaction signing flow with backend preflight simulation.
    • Soroban event emission -> Indexer worker -> PostgreSQL -> SSE/WebSocket fanout.
    • Webhook retry with exponential backoff and dead-letter triage.

Target Files

  • docs-site/mint.json (or Docusaurus config)
  • docs-site/pages/quickstart.mdx
  • docs-site/pages/contracts/lifecycle.mdx
  • docs-site/pages/api-reference/
  • .github/workflows/deploy-docs.yml

Acceptance Criteria

  • Documentation site compiles without broken links or missing assets.
  • Interactive API console allows executing live requests against testnet/mock endpoints.
  • Mermaid sequence diagrams clearly depict core protocol architectures.
  • Comprehensive TypeScript, Python, and cURL code samples provided for every major operation.
  • Automated CI workflow deploys documentation preview on pull requests.

Activity

bashco-web commented on Sep 27, 2026

@bashco-web

@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 commented on Sep 27, 2026

@Saintricks

@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
Contributor

@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.

drips-wave commented on Sep 27, 2026

@drips-wave

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 🌊

added a commit that references this issue on Oct 6, 2026

drips-wave commented on Oct 6, 2026

@drips-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions