Skip to content

MRWK bounty: 125 MRWK - site UX and functional improvements, round 2 #577

@ramimbo

Description

@ramimbo

Reward: 125 MRWK per accepted award
Max awards: 5

Work Needed

Improve the public MergeWork site experience with focused visual, usability, accessibility, or functional enhancements. Accepted work should make a real contributor, maintainer, wallet, bounty, explore, activity, or proof workflow easier to use.

Useful accepted work can include:

  • Improve bounty, explore, activity, account, wallet, proof, public docs, or public navigation pages.
  • Add useful filters, empty states, status summaries, sort controls, or clearer proof/bounty/account links where the current site already exposes the data.
  • Improve responsive layout, accessibility, readability, form feedback, or error states for an existing public workflow.
  • Make visual improvements that also improve scanning, comparison, navigation, or task completion.
  • Add or update focused tests for changed page behavior, links, rendering, forms, or public route output.

Acceptance Criteria

  • Open a focused PR that links this issue with Bounty #<issue number> or Refs #<issue number>.
  • Keep the change focused on one coherent page, workflow, or reusable UI pattern.
  • Include concise before/after notes and screenshots for visual layout changes.
  • Add or update tests when behavior, routes, rendered fields, links, forms, or public data output change.
  • Run the relevant focused tests and applicable project checks for the touched area.
  • Existing checks pass.
  • One award per distinct useful site or workflow improvement.

How To Submit

Open a focused PR with the required evidence. A maintainer must apply mrwk:accepted or record an admin payout before payment.

Evidence or Tests Required

  • Link the PR and the source issue.
  • Describe the user-facing workflow improved.
  • Include screenshots for visual layout changes when relevant.
  • List focused tests and project checks run.

Out of Scope

  • Duplicate page restyles or repeated versions of already accepted work.
  • Decorative-only changes that do not improve scanning, navigation, or task completion.
  • Broad redesigns, unrelated refactors, copy-only churn, or changes that reduce clarity.
  • Private keys, seed material, wallet JSON, browser storage, cookies, OAuth state, access tokens, signatures, private vulnerability details, deployment credentials, price claims, investment claims, liquidity claims, bridge promises, exchange claims, cash-out claims, or fabricated payout claims.

Duplicate and Stale Work Rules

Duplicate work is judged by the first useful, reviewable submission that matches the bounty criteria. Stale claims may be released or ignored when they lack reviewable evidence, no longer match current repository behavior, overlap a merged PR, or fail to respond to maintainer review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfrontendUser-facing HTML or UIhelp wantedExtra attention is neededmrwk:bountyMRWK bounty is postedmrwk:paidLedger payment recorded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions