Hunting Team Portal Documentation

This documentation is intended to make the project maintainable if the original developer leaves the club.

Start Here

1. Read architecture.md for the system boundaries.
2. Read development.md to run the project locally.
3. Read roles-and-permissions.md before changing Directus permissions.
4. Read operations.md before deploying or upgrading anything.
5. Read feature-status.md for implemented and planned work.

Design Principles

• Members and application administrators use the custom frontend.
• Directus Studio is a technical back office, not the normal member interface.
• Directus permissions are the security boundary; frontend visibility checks are only usability.
• Credentials belong in environment variables and must never be committed.
• Major features should be separate commits with tests and documentation.