Skip to content

Add submission standards section to landing page#119

Open
Chenxizhe2025 wants to merge 1 commit into
gibwork:mainfrom
Chenxizhe2025:codex/submission-quality-section
Open

Add submission standards section to landing page#119
Chenxizhe2025 wants to merge 1 commit into
gibwork:mainfrom
Chenxizhe2025:codex/submission-quality-section

Conversation

@Chenxizhe2025

Copy link
Copy Markdown

Summary

  • add a new Proof that gets approved landing page section that explains the review loop behind Gibwork tasks, bounties, and services
  • show concrete submission standards: public links, screenshots/files, a short rationale, and no duplicate or copy-paste submissions
  • keep the change scoped to one new component plus the homepage insertion point, with no new dependencies

Why this helps the landing page

The current homepage explains that users can create or complete work, but it does not clearly show what makes work reviewable and payout-ready. This section makes the platform feel more operationally current by showing both sides of the marketplace how clear scope, verifiable proof, quality checks, and wallet payouts connect.

Verification

  • npm run build passes
  • git diff --check passes
  • local production preview at http://localhost:3107/#proof returns 200 and includes the new section text
  • Chrome desktop screenshot check: proof section renders with the checklist and four cards visible
  • Chrome mobile screenshot check: section stacks cleanly at 390px width without text overlap

Task context

Submitted for the funded Gibwork task: Improve Gibwork Landing Page or Submit a GitHub Enhancement.
Task URL: https://app.gib.work/tasks/b7c2a3c9-c412-4613-9cfb-d8a5f54d14b7

@vercel

vercel Bot commented Jun 20, 2026

Copy link
Copy Markdown

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