How gnyblast/futsal-team-builder works
Project type and purpose
• This is a single-page front-end application (Angular 17 + Angular Material) called “Futsal-Team-Builder.”
• Its sole purpose is to generate and display balanced football teams in the browser, with optional persistence (via Firestore).
File structure
• Top-level files: configuration (.gitignore, angular.json, tsconfig.json), Docker/Podman build files, CI workflow (.github/workflows/build-and-release.yml), README.
• src/app/: the heart of the SPA.
• components/: the visual UI blocks (login, register, main view, drawer, navbar, confirmation dialog).
• services/: encapsulated logic (authentication, dialog management, drawer state, Firestore I/O, player data, team-generation algorithm).
• directives/, enums/, interfaces/: cross-cutting Angular utilities and type definitions.
• material.module.ts: Angular Material imports consolidation.
• src/assets/: static test data (test_players.json).
• src/environments/: build-time environment configs.
• Docker and Podman containerization folders (docker/Dockerfile, podman/Containerfile) enable both dev server and production build.
• CI pipeline defined under .github/workflows.
README for additional insights
• Confirms purely a front-end Angular SPA (no custom backend code).
• Supports local dev (npm start), containerized dev (Docker/Podman), production build (Angular CLI + container).
• Live URL provided.
• Demo data auto-populated from src/assets/test_players.json.
Detail without overthinking
• Critical paths: user interactions, data flow, build/deploy steps.
• Keep it organized: group related components/services under a single “Angular App” boundary.
• Non-obvious dependencies (e.g., FirestoreService requires environment variables).
• The goal is maximum clarity on how UI, business logic, data, and deployment interact in this SPA.