Skip to content

ROADMAP.md

Latest commit

 

History

History
79 lines (59 loc) · 3.22 KB

ROADMAP.md

File metadata and controls

79 lines (59 loc) · 3.22 KB
Raw

SignalFlow Studio Roadmap

SignalFlow Studio should become a focused, useful open-source autoposting workspace rather than a bundle of demos.

Product Bet

Build for creators, builders, developers, founders, maintainers, and small teams who want to post publicly without manually writing every caption, recording every asset, creating every GIF, and formatting every channel by hand.

The one-line promise:

Describe once, add data or media, and generate formatted posting packages for selected social accounts.

MVP Workflow

  1. User describes what should be posted.
  2. User adds any useful data, links, files, repository context, screenshots, or screen recordings.
  3. SignalFlow Studio builds a formatted package for selected social accounts.
  4. SignalFlow Studio creates:
    • platform-specific post variants,
    • captions and long-form drafts,
    • visual media plan,
    • generated card asset,
    • screenshot/recording/GIF handoff,
    • model prompt,
    • Markdown and JSON exports.
  5. Publishing stays reviewable through manual copy, webhooks, or official APIs.

Priorities

1. Make the First Run Excellent

  • Replace placeholder repo paths with a guided empty state.
  • Show one primary action: "Generate full post package".
  • Keep the hosted product as one Next.js app with standalone API routes.
  • Save outputs into one timestamped folder.
  • Include a sample repo/demo mode so visitors can try the product in one minute.
  • Add copy/export actions for every generated draft and asset.

2. Make the Core Engine Trustworthy

  • Improve file ranking with git diff awareness.
  • Ignore generated, lock, minified, vendored, and binary-heavy files.
  • Add tests for repo scanning, pipeline output shape, and API routes.
  • Avoid arbitrary shell command execution in default demos.
  • Make terminal recording opt-in and clearly labeled.

3. Make Outputs Worth Sharing

  • Add platform presets: X, LinkedIn, Instagram, blog intro, newsletter, and release notes.
  • Add tone controls: technical, founder, DevRel, concise.
  • Add editable templates before export.
  • Improve code image themes and dimensions.
  • Generate a Markdown posting package alongside JSON.
  • Add official-API draft publishing helpers for supported platforms.

4. Make It Contributor Friendly

  • Add screenshots or a short demo GIF to the README.
  • Add issue templates for bugs, feature requests, and good first issues.
  • Add CI for the hosted app build and engine tests.
  • Document architecture in docs/architecture.md.
  • Publish a small set of labeled starter issues.
  • Keep internal engine modules stable so integrations can plug into the hosted app cleanly.

What Not To Build Yet

  • Unreviewed auto-posting to social platforms.
  • Complex cloud accounts.
  • Browser/session scraping.
  • A large multi-language native stack before the one-app Next.js product feels great.

Good First Issues

  • Add a --since option that uses git diff to rank recently changed files.
  • Add a Markdown export next to pipeline_summary.json.
  • Add richer LinkedIn/X/Instagram post templates to the local stub.
  • Add frontend error states for failed standalone generation responses.
  • Add a sample project fixture for demos and tests.
  • Add OAuth-backed draft publishing adapters behind explicit user approval.