Bring the events module to production readiness

[Lakes41]

Difficulty: Advanced | Type: Feature

Background: NEXT_PUBLIC_FEATURE_EVENTS defaults to true in mock mode but false in prod, gating /events/*, implying the events module exists but isn't yet considered production-ready.

Problem: Without a documented reason the events module is prod-disabled, contributors have no clear target for what "done" looks like — the gap between "works in the demo" and "safe to ship" needs to be made explicit and closed.

Expected Outcome: A documented gap analysis between the current /events/* implementation and production requirements (error handling, empty/loading states, real data validation, access-gating correctness), followed by fixes closing that gap, with the flag flipped to true by default in prod once complete.

Suggested Implementation: Audit /events/* pages against the same production bar as the member/admin dashboards (loading states, error boundaries, gated-access correctness per resource policy), fix identified gaps, and update the default in lib/features.ts and .env.example once the module passes review.

Acceptance Criteria:

• A short audit doc/PR description lists every gap found and how each was addressed.
• Events pages have equivalent loading/error/empty-state handling to the rest of the app.
• Default flag value is flipped to true for prod only after the above is complete and reviewed.

Likely Affected Files/Directories: app/events/*, lib/features.ts, .env.example

Labels: feature, GrantFox OSS, Maybe Rewarded, Official Campaign | FWC26

[guptakumarranjeet150]

Hello @maintainers,

I can tackle Bring the events module to production readiness. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in Adamantine-guild/guildpass-integrations
• Implementation: Build Bring the events module to production readiness with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• PR: Atomic commit with clean git hygiene and passing CI

I am ready to start immediately—please assign this to me!

[ranjeet150]

Hi everyone,

I would love to take this on. My planned approach:

• Build Bring the events module to production readiness with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Add component unit tests and ensure zero TypeScript/ESLint warnings.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[shobhamerabacha-star]

Hi maintainers,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Build Bring the events module to production readiness with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

I am ready to start immediately—please assign this to me!