Implement Structured Submission Flow

[Benjtalkshow]

Implement Structured Submission Flow for each bounties in bounty details page (/bounty/bountyId)

Create structured submission UI instead of plain textarea.

Expected Data Types

type SubmissionForm = {
  githubUrl?: string
  demoUrl?: string
  explanation: string
  attachments?: string[]
  walletAddress: string
}

UX Requirements

• Validations
• Save draft option
• Clear success state

Acceptance Criteria

• Form validates correctly
• Errors handled gracefully

[linear]

BOU-84

[coderabbitai]

🔗 Related PRs

#56 - feat: Implementation of bounty participation & submission backend logic [merged]
#73 - feat: Extend Form Components for Bounty Creation [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[odeyemitobi]

@odeyemitobi has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @odeyemitobi to this issue.

[teethaking]

@teethaking has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Why I’d like to work on this issue:
I am interested in implementing the Structured Submission Flow because it is vital for standardized data collection and a professional user experience on the bounty details page. Moving away from a plain textarea to a structured SubmissionForm will significantly reduce back-and-forth between hunters and maintainers by ensuring all critical data—like GitHub URLs and wallet addresses—is captured correctly at the point of entry.

Relevant Experience:

Complex Form Handling: Expert in building multi-input forms using React Hook Form or Formik, ensuring seamless state management for optional and required fields.

Validation Logic: Proficient in implementing real-time schema validation (Zod/Yup) to handle URL formats, string length for explanations, and cryptographic address checksums.

State Persistence: Experience building "Save Draft" functionality using localStorage or backend-synced drafts to prevent data loss during long-form entries.

UI/UX Polish: Skilled in creating clear success states and graceful error handling to guide users through the submission lifecycle.

Implementation Plan
I will focus on the following technical components:

Schema Definition: Create a Zod schema for the SubmissionForm type to handle strict validation for githubUrl, demoUrl, and walletAddress.

Draft Logic: Implement a useEffect hook to persist form state to localStorage, allowing users to leave and return to their submission.

File Uploads: Build a robust attachment handler for the attachments array, including file type and size constraints.

User Feedback: Design a high-visibility success state and field-level error messaging to meet the Acceptance Criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @teethaking to this issue.

[lynaDev2]

@lynaDev2 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I’d like to work on #81 – Implement Structured Submission Flow for the bounty details page.

I have experience building structured forms using React, Tailwind CSS, and React Hook Form, including validation, error handling, draft persistence, and clean UX. I’ll implement the required schema fields, add proper validations, save draft support, and clear success/error states with reusable components.

I can start immediately and will follow the project standards.

Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @lynaDev2 to this issue.

[rejoicetukura-blip]

@rejoicetukura-blip has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I am deeply interested in working on this issue because I believe it sits at the intersection of impact and execution. Addressing this challenge requires not only strategic thinking but also consistent operational support — and that is where I thrive. I am motivated by opportunities where structured systems, clear communication, and organized execution can create measurable results.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @rejoicetukura-blip to this issue.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave