Build the analytics module scaffold behind its feature flag

[Lakes41]

Difficulty: Advanced | Type: Feature

Background: NEXT_PUBLIC_FEATURE_ANALYTICS exists in the feature-flag table, defaulting to false in every environment, and "Advanced analytics" is explicitly listed under "Deferred (intentionally)."

Problem: There's currently no analytics module at all to gate — the flag exists as a reserved placeholder with nothing behind it, meaning the flag's "Feature unavailable" state is the entire experience today.

Expected Outcome: A first working version of the analytics module exists (e.g. membership growth over time, resource access frequency, role distribution), rendered only when the flag is explicitly enabled, using data available from existing endpoints (GET /v1/members, GET /v1/admin/events) without requiring new backend work.

Suggested Implementation: Add an app/admin/analytics/ route wrapped in <FeatureGate enabled={features.analytics} name="Analytics">, compute simple aggregate charts client-side from existing member/event data (e.g. using a lightweight charting library), and add the nav entry filtered by the flag per the existing pattern.

Acceptance Criteria:

• Analytics page renders real, correctly computed aggregates from mock-mode data.
• Page and nav entry are fully hidden when the flag is off (default), consistent with other gated modules.
• At least two distinct chart/metric views are implemented (not a single placeholder number).

Likely Affected Files/Directories: app/admin/analytics/ (new), lib/features.ts, components/nav.tsx

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

[didi168]

I'd like to work on this feature.

I noticed the analytics flag already exists, but there's currently no functionality behind it, which makes this a good opportunity to turn the placeholder into a useful gated module without requiring backend changes. My plan is to build an analytics page powered by existing member and event data, generating meaningful aggregates such as membership growth, role distribution, and activity trends.

I'll ensure the page and navigation entry remain completely hidden when "NEXT_PUBLIC_FEATURE_ANALYTICS" is disabled, following the existing feature-gate pattern. For the analytics view itself, I'll implement multiple metrics/charts rather than placeholders and verify that the calculations are derived correctly from the available data sources, including mock mode.

I have experience building React/Next.js dashboards, feature-flagged modules, and data visualizations, and I can deliver a clean, maintainable implementation aligned with the acceptance criteria.

[grantfox-oss]

🦊 GrantFox — @didi168 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #249)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@didi168's PR #310 was approved and merged by @Lakes41.

🏆 @didi168: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (156 total points). Track your full progress on GrantFox.

👏 Great work, @didi168! Keep contributing to Adamantine-guild.