Add a Work Proof Loop section to explain funded submissions and payouts

[trejospeed-hash]

Summary

This is a focused landing-page enhancement proposal for the funded Gibwork task:
https://app.gib.work/tasks/b7c2a3c9-c412-4613-9cfb-d8a5f54d14b7

I recommend adding a Work Proof Loop section that explains the current Gibwork product in the language users see inside the app: funded work, proof submissions, review, and wallet payout.

Supporting proposal + mockup:
https://gist.github.com/trejospeed-hash/bce099c4c3e7fa244c3cd7274d896f3d

Mockup SVG:
https://gist.githubusercontent.com/trejospeed-hash/bce099c4c3e7fa244c3cd7274d896f3d/raw/c151aaa439a554e2e4403b31d15f3ecf39e2eafc/work-proof-loop-mockup.svg

Problem

The public landing page currently does a good job stating the broad promise: find talent, find work. But the live app is more concrete than that. A new user sees:

• funded tasks with USDC/SPL-token rewards,
• categories like Development, Feedback, Social Media, Design, and Open Source,
• proof-based submissions such as GitHub PRs/issues, screenshots, public URLs, recordings, or uploaded media,
• review/approval before payout.

That proof-based workflow is the product's strongest differentiator, but it is not explained clearly enough before users click into the app.

Proposed Enhancement

Add a section after the hero, or before Get help from an expert, titled:

Post work. Submit proof. Get paid onchain.

The section should include four parts:

1. Live funded-work cards
   Show 2-3 current or fallback examples with category, reward amount, deadline, and proof type.

2. The proof loop
   A four-step row:

   • Choose funded work
   • Submit proof
   • Get reviewed
   • Receive wallet payout

3. Submission quality checklist
   Explain what good submissions include: public link, screenshots, PR/issue URL, task-specific evidence, no spam or recycled content.

4. Dual CTA row
   Primary: Explore funded work
   Secondary: Create a task and Download mobile app

Suggested Copy

Gibwork turns work into verifiable submissions. Projects fund tasks or open-source bounties. Contributors submit proof such as a PR, issue, screenshot, public URL, or media file. Once approved, the reward is released to the contributor wallet.

Why This Is Different From Existing Proposals

Several open issues already cover broad hero refreshes, mobile visibility, or live listing cards. This proposal is narrower: it focuses on the missing proof-submission and payout explanation that connects the marketing page to the actual app workflow.

It can be implemented independently, or combined with a broader landing-page refresh.

Acceptance Criteria

• The landing page explains the task/bounty proof workflow in plain language.
• The section distinguishes discovery from approval, so users understand that payout follows accepted proof.
• Mobile layout stacks cleanly: intro, cards, proof loop, CTA.
• Desktop layout uses a compact row/grid without adding heavy visual clutter.
• If live /api/explore data is used, provide a static fallback so the page still builds and renders when the API is unavailable.
• CTA links point to the relevant app destinations.

Implementation Notes

Potential files/components:

• Add a WorkProofLoop or similarly named landing-page component.
• Reuse existing design tokens and card/button primitives.
• Use the existing app marketplace categories and reward labels as content references.
• Keep the copy concise so it improves conversion without turning the homepage into documentation.

[Kaustubhh-Deshmukh-Git]

Claiming this. Will submit PR shortly.