This is a bounty to implement a settings page for a web application, specifically replacing a placeholder with a static but actionable overview of account, notification, security, and billing preferences. The task is scoped to frontend implementation, using mock data, and maintaining the existing style. This is a clear, paid deliverable.
A starter prompt for Claude Code, what you'll need, and how to reach them.
You are an expert Next.js and React developer. Fork the GitHub repository `SecureBananaLabs/bug-bounty`. Your task is to implement the `/settings` page according to issue #1795. Specifically, replace the placeholder card in `apps/web/app/settings/page.tsx` with a static, but actionable, settings overview. This page should include distinct sections for 'Account/Profile', 'Notifications', 'Security', and 'Payout/Billing Preferences'. Within each section, add mock status chips (e.g., 'Email Verified', '2FA Enabled', 'Notifications On') and 'next action' controls (e.g., 'Edit Profile', 'Manage Notifications', 'Change Password', 'Update Payment Info'). Ensure the new UI adheres to the existing frontend styles of the `SecureBananaLabs/bug-bounty` project and uses mock data only, making no changes to API behavior. Focus on clean, modular React components within the Next.js App Router structure. Your goal is to deliver a PR that visually completes the settings page as described in the issue. Upon completion, provide the updated `page.tsx` file and any new shared components or CSS rules.
Bounty (amount on the issue). ## Bug The `/settings` route currently renders a single placeholder card instead of useful account controls. The page says account preferences, profile visibility, and security controls live there, but it does not expose any concrete settings, statuses, or next actions. ## Impact - Users can navigate to settings but cannot inspect profile visibility, notification preferences, security posture, or billing defaults. - The route feels unfinished compared with the rest of the marketplace shell. - Important account state is not scannable from the page. ## Expected behavior `/settings` should render a static but actionable settings overview matching the current frontend style, including account/profile, notifications, security, and payout/billing preference sections. It should use mock data only and avoid changing API behavior. ## Scope - Replace the placeholder settings card with a useful static settings overview. - Add status chips and next-action controls for account, notification, security, and billing/payout preferences. - Keep the change scoped to `apps/web/app/settings/page.tsx` and shared page styles if needed. This issue is limited only to the creat
Standard for any developer.
Standard Next.js development environment.
Operator's core stack.
Common styling framework, likely used in the target repo.
Create a new issue on the `SecureBananaLabs/bug-bounty` repository, stating your intent to work on this, referring to issue #1795, and requesting confirmation from the maintainer for a duplicate bounty.
“I've reviewed issue #1795 for the `/settings` page and can implement the static settings overview, including account, notification, security, and billing sections with mock data, matching existing styles. I've successfully built similar interfaces using Next.js and React. Could I create a new issue to claim this bounty?”
Open the original ↗