Skip to content

Refresh landing page: reflect current product, add mobile app section - #191

Open
daliquido wants to merge 1 commit into
gibwork:mainfrom
daliquido:landing-page-refresh
Open

Refresh landing page: reflect current product, add mobile app section#191
daliquido wants to merge 1 commit into
gibwork:mainfrom
daliquido:landing-page-refresh

Conversation

@daliquido

Copy link
Copy Markdown

Summary

The Gibwork landing page was positioning the product as a crypto/open-source-bounty tool ("Find Talent, Find Work," GitHub-issue-focused FAQ) with no mention of the mobile app. The actual current product is a broader task/bounty marketplace — available on iOS and Android with a 4.9★ rating (179 reviews) — covering content, design, marketing, writing, product testing/UX, and more, not just open source. This PR updates the landing page copy, adds a dedicated mobile app section, and refreshes category/FAQ content to match what Gibwork actually is today.

What changed

Hero (components/hero.tsx)

New headline and subhead reflecting the broader range of paid work (content, design, marketing, writing, etc.), not just open source bounties
Added App Store and Google Play badges

New mobile app section (components/mobile-app.tsx)

New "Take Gibwork with you" section highlighting the mobile app, its 4.9★ rating, and core app functionality (browse tasks, submit work, track earnings)
Inserted into the page between the "Looking for Help/Work" and Testimonial sections (app/page.tsx)

Category cards (components/looking-for.tsx)

Replaced generic "Simple Task"/"Services" cards with categories that reflect the real product: Content & Social, Design & Creative — while keeping Open Source Bounty as a differentiator
Updated tab intro copy

FAQ (components/faq.tsx)

Revised the bounty vs. task definition, which was overly GitHub-specific, to reflect the platform's broader scope
Added a new FAQ item: "Can I use Gibwork on mobile?"

Nav & footer (components/nav.tsx, components/footer.tsx)

Added links to the mobile app

Site config (lib/site-config.ts)

Updated site description (was crypto/Q&A-focused, now reflects the current task marketplace)
Added iosAppUrl and androidAppUrl
Why this matters

The landing page is most people's first impression of Gibwork, and it currently undersells and misrepresents the product — no mention of the app despite it having real usage and a strong rating, and copy that frames the platform as narrower (open-source/crypto-only) than it actually is. This update makes the page an accurate, more complete reflection of what users get today, and surfaces the mobile app as a credibility signal (4.9★, 179 reviews) that wasn't being used anywhere on the site.

Testing
npm install && npm run build — builds clean, no type errors
Verified locally on localhost:3000 across desktop and mobile viewport widths
Confirmed App Store and Google Play badge links resolve to the correct listings
Screenshots attached below (desktop + mobile: hero, mobile app section, category cards, FAQ)
Notes for reviewers
The category card images (simple_task.png, services.png) are reused existing CDN assets — new imagery could be created by design if this direction is approved, since content_social.png/design_creative.png don't currently exist on the CDN
App Store and Play Store badge SVGs are placeholders; recommend swapping in official badge assets from Apple's and Google's brand guideline kits before merging to production

Screenshot 2026-08-19 at 21 15 10 Screenshot 2026-08-19 at 21 13 54 Screenshot 2026-08-19 at 21 10 59

- Update hero headline/subhead to reflect broader task categories
- Add App Store and Google Play badges to hero
- Add new mobile app highlight section
- Update category cards (Content & Social, Design & Creative, Open Source Bounty)
- Update FAQ: revised bounty/task definition, added mobile app FAQ
- Add app links to nav and footer
- Update site description in site-config.ts
@vercel

vercel Bot commented Aug 19, 2026

Copy link
Copy Markdown

@daliquido 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