Skip to content

Add live work proof section with current funded task examples #124

Description

@kgy7247

Summary

Add a "Live Work Proof" section to the Gibwork landing page that shows a small, rotating sample of currently funded marketplace tasks and explains the contributor proof loop: find task -> ship artifact -> submit public proof -> get reviewed/paid.

This is intentionally narrower than a full landing-page redesign. The current open issue list already has many broad "modernize the landing page" proposals, so this suggestion focuses on one conversion gap: visitors cannot immediately see concrete, current work examples or understand what a strong submission package looks like.

Why this improves the landing page

The homepage currently positions Gibwork as a work marketplace, but a new visitor still has to infer:

  • what kind of work is active right now
  • whether rewards are funded and time-sensitive
  • what a good submission artifact looks like
  • how social/content tasks differ from development tasks
  • why Gibwork is credible for both human contributors and AI-assisted contributors

A compact live-proof section would make the product feel active immediately and reduce the gap between "interesting marketplace" and "I can do one task today."

Proposed section

Title: Funded work, visible before you sign in

Content blocks:

  1. Live examples

    • Show 3-6 current tasks pulled from the public marketplace feed.
    • Include title, category, reward pool, deadline, and task type.
    • Filter out closed tasks and hidden tasks.
  2. Submission proof loop

    • One row explaining the path:
      • Choose a task
      • Create the public proof artifact
      • Submit link/screenshots/PR
      • Wait for sponsor review
  3. Task quality hints

    • Short guidance for common task types:
      • Social/video: public URL, screenshots, engagement evidence
      • Development: issue/PR URL, validation commands, screenshots
      • Feedback/QA: annotated screenshot, specific findings, quick win
  4. AI-assisted contributor framing

    • Add a neutral note that AI-assisted contributors are welcome when submissions are original, verifiable, and task-specific.
    • This should not promise acceptance; it should clarify quality expectations.

Implementation sketch

Use the existing public task data already exposed by the marketplace feed. A static fallback can be bundled for SEO or build failures.

Pseudo-flow:

const tasks = await fetch("https://app.gib.work/api/explore").then(r => r.json());

const visible = tasks.results
  .filter(task => task.isOpen && !task.isHidden && task.remainingAmount > 0)
  .slice(0, 6);

Suggested card fields:

  • title
  • tags
  • remainingAmount
  • asset.symbol
  • deadline
  • type

Mock/reference

I made a small static reference page that demonstrates the same idea with public data and no private credentials:

https://kgy7247.github.io/ai-bounty-radar/

Repository:

https://github.com/kgy7247/ai-bounty-radar

The reference is intentionally simple: a live opportunity table, a same-day submission-pack service framing, and a daily refresh workflow. Gibwork's official implementation should be cleaner and native to the existing design system, but this shows the conversion concept with working data.

Acceptance criteria

  • Landing page includes a compact "Live Work Proof" or equivalent section.
  • Section displays current open task examples or a safe static fallback.
  • Closed, hidden, and zero-remaining tasks are not shown.
  • Each displayed example links into the relevant task detail page.
  • Copy explains what evidence a strong submission should include.
  • The section works on mobile without pushing the main CTA too far down.
  • No "guaranteed earnings" or investment-like language is introduced.

User benefit

Contributors can quickly decide whether Gibwork has real tasks worth attempting today. Sponsors see that tasks become concrete public proof artifacts, not just vague marketplace listings. This should improve trust and first-session conversion without requiring a full homepage rewrite.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions