## FRONTEND: Discover Page — Filter Sidebar Not Visible on Mobile (Layout Bug)

[OSEH-svg]

Description
The FilterSidebar component (components/events/filter-sidebar.tsx) is a fully implemented filter UI, but it is only rendered in the desktop layout. On mobile viewports, the filter sidebar is not accessible as a drawer or bottom sheet. Users on mobile cannot filter events.

Tasks

• Implement a mobile-accessible filter entry point (e.g., a "Filter" button that opens a bottom sheet or full-screen modal).
• Reuse FilterSidebar inside a Drawer or Overlay component.
• Preserve filter state when the drawer closes.
• Test on a 375px (iPhone SE) viewport.
  Acceptance Criteria
• A "Filter" button is visible on mobile viewports.
• Tapping it opens the filter UI in a drawer or modal.
• Filter state is preserved when the drawer is closed and reopened.
• No horizontal overflow on 375px viewport.

[d3vobed]

Hi, id like to work on this issue assign me and et's begin

[dehonesty2-svg]

I’d like to work on this issue.

I have experience building responsive React/Next.js interfaces and fixing mobile-specific layout and usability issues while keeping components reusable and maintaining existing state management.

For this task, I plan to:

• Add a mobile-only Filter button that is visible on small viewports.
• Reuse the existing FilterSidebar inside a Drawer or modal component instead of duplicating the filter UI.
• Ensure filter selections persist when the drawer is closed and reopened by leveraging the existing state.
• Verify there is no horizontal overflow and test the implementation on a 375px (iPhone SE) viewport.
• Keep the desktop experience unchanged and ensure the solution is clean, accessible, and responsive.

I'll provide a focused implementation with attention to UI consistency, accessibility, and maintainability. I'd be happy to take this on.

[Samuel1-ona]

@Samuel1-ona has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I can work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samuel1-ona to this issue.

[drips-wave]

Congratulations, @Samuel1-ona! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Samuel1-ona: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Samuel1-ona as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Samuel1-ona: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.