Skip to content

Improve landing page product positioning - #132

Open
Difficult-Burger wants to merge 1 commit into
gibwork:mainfrom
Difficult-Burger:bounty/gibwork-product-flow
Open

Improve landing page product positioning#132
Difficult-Burger wants to merge 1 commit into
gibwork:mainfrom
Difficult-Burger:bounty/gibwork-product-flow

Conversation

@Difficult-Burger

Copy link
Copy Markdown

Summary

This updates the landing page so it better reflects the current Gibwork product: funded crypto bounties, tasks, services, verified submissions, wallet-native payouts, and mobile-friendly contributor workflows.

Changes

  • Repositions the hero from a generic talent marketplace message to a clearer funded-work/proof/payout message.
  • Adds a new ProductFlow section that explains the creator and contributor workflow:
    • create funded work
    • collect reviewable submissions
    • approve and pay via wallet-native rewards
  • Updates the LookingFor section copy and sample work items to match GitHub PR bounties, product walkthroughs, and USDC rewards.
  • Updates site metadata to match the new positioning.
  • Adds accessible labels for the mobile navigation open/close controls.

Verification

  • npx tsc --noEmit
  • git diff --check
  • Local browser QA at http://localhost:3020
    • desktop hero renders with the updated positioning
    • desktop workflow section renders without overlap
    • mobile hero wraps cleanly at 390px width
    • mobile workflow cards stack cleanly
    • mobile navigation menu opens and shows expected links

Notes

npm run build is currently blocked locally by next/font timing out while fetching Inter from Google Fonts. The app runs in dev after Next falls back to a local font, and the TypeScript check passes. This appears unrelated to this PR because the font import already exists in app/layout.tsx.

@vercel

vercel Bot commented Jul 4, 2026

Copy link
Copy Markdown

@Difficult-Burger is attempting to deploy a commit to the gibwork Team on Vercel.

A member of the Team first needs to authorize it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant