Add typed feature flags for incomplete modules

[Lakes41]

Difficulty: Hard

Type: Feature

Summary

Add feature flags for modules that may be experimental or not yet production-ready, such as events, resources, analytics, and advanced admin tooling.

Current Behaviour

Navigation and pages may expose MVP, demo, or future-facing sections without a central feature flag model.

Expected Behaviour

Maintainers should be able to enable or disable major modules through documented environment variables.

Suggested Implementation

Create a typed feature flag module that reads public environment variables and exposes explicit booleans. Use the flags in navigation, page guards, and demo-only flows.

Files or Areas Likely Affected

• lib/features.ts
• components/nav.tsx
• app/events/**/*.tsx
• app/resources/**/*.tsx
• app/admin/**/*.tsx
• .env.example
• README.md

Acceptance Criteria

• Feature flags are parsed through a typed module
• Disabled modules are hidden from navigation
• Disabled routes render a clear unavailable state or redirect safely
• Local mock mode can enable demo-only features
• README documents recommended production defaults

Additional Notes

Do not introduce a remote feature flag service unless maintainers explicitly request it.

[ekwe7]

I would love to work on this issue. I have experience building production ready applications and collaborating through GitHub workflows. I'll carefully analyze the current implementation, propose a reliable solution, and submit a well-tested PR. My focus is on clean code, maintainability, and timely delivery

[Babigdk]

I’d like to work on this issue.

I have experience implementing typed feature-flag systems in TypeScript/Next.js applications, especially for controlling incomplete or experimental modules without exposing unstable routes in production.

For this task, I will:

• Create a strongly typed "lib/features.ts" that reads and validates environment variables into explicit booleans
• Integrate flags into navigation ("components/nav.tsx") to conditionally hide disabled modules
• Add route-level guards for "events", "resources", "admin", and other gated sections with safe fallback states or redirects
• Support a mock/local mode that can enable demo-only features without affecting production configuration
• Update ".env.example" and "README.md" with clear documentation and recommended defaults
• Ensure consistent behavior across both mock and live environments without introducing any remote feature-flag dependency

The goal is a clean, predictable, and maintainable feature-flag system that prevents accidental exposure of incomplete modules while remaining easy for maintainers to extend.

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[MarcusDavidG]

I can handle this issue and will like to work on it, Please assign thank you.

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.