How damiannortega/gym works
Project type and purpose
• This is a single-page application (SPA) built with Angular. The README (# Gym) and the directory names suggest it’s the front-end client for a “Gym” website: rendering home, classes, class details, login/inscription pages, contact forms, etc.
• There is no server-side code here—data comes either from static JSON in public/json/clases.json or from external REST endpoints configured in src/app/app.config.ts.
File structure
• Top-level files:
• angular.json, tsconfig*.json → Angular workspace configuration
• src/ → Angular application source
• public/ & docs/browser/ → static assets & prerendered build output
• Inside src/app/ you see:
• components/ → reusable UI pieces (header, footer, opiniones)
• pages/ → route-driven views (home, clases, clase-detalle, login, inscripcion, contacto, admin-* pages)
• services/ → business logic & HTTP clients (AuthService, ClasesService, StorageService)
• guards/ → route protections (AuthGuard)
• pipes/ → data transformation (DomSeguro, ObjetivoResaltado)
• shared/ → cross-cutting UI components (carousel, buscador, class-card, faq, hero, etc.)
• Configuration and entry points:
• src/main.ts → bootstraps AppModule
• src/app/app.routes.ts → defines application routes
• src/app/app.module.ts (implied) → declares & wires up components, services, guards, pipes
Key insights from the README
• Very minimal—only the project title. But combined with the file tree, we know this is a static Angular front-end, likely deployed as a set of HTML/CSS/JS files (see public/ & docs/) fetching data from static JSON or external APIs.
Elements
• Blue for UI components/pages
• Green for services & guards
• Orange for external systems (API, Static Server)
• Gray for utilities (pipes, storage)