How machado211993/municipalidad_loreto works
Project type and purpose
• This is a single‐page web application (SPA) built entirely in Angular (v18.2.8).
• It contains no backend code; it’s designed to be compiled into static assets and served by any static file host (Netlify, AWS S3, GitHub Pages, etc.).
File structure
• src/ : all application‐specific code
• src/app/ : the Angular AppModule, subdivided into “components” (reusable UI widgets: header, footer, mapa, video) and “pages” (route‐driven views: home, novedades, contacto, etc.).
• src/assets/ : images and video content.
• src/global_styles.css : global stylesheet.
• src/index.html + src/main.ts : Angular bootstrap.
• public/ : any extra files to be copied to the dist folder.
• angular.json + tsconfig*.json : build & TypeScript configuration.
• dist/demo/browser/ : post‐build output (index.html, main.js, polyfills.js, scripts.css, styles.css, assets, etc.).
README
• Confirms use of Angular CLI for dev server (ng serve), building (ng build), and testing (Karma, e2e).
• No mention of backend, so the only “external services” would be static file hosting or optional third‐party APIs.
Main components and their relationships
a. Developer Environment & Build Pipeline
• Angular CLI (ng serve/build)
• TypeScript compiler & Webpack bundler
• Output → dist/demo/browser
b. Deployment / Hosting
• Static Web Server or CDN serving index.html + JS/CSS bundles + assets
c. Client Side (Browser)
• Angular bootstrap & AppModule
• Angular Router (handles /home, /contacto, /tramites, etc.)
• Components & Pages (header, footer, mapa, video loaded into router‐outlet)
• Static assets fetched from /assets/images and /assets/video
Architectural patterns & design principles
• Modular structure: Components (UI pieces) vs. Pages (route compositions).
• Single Responsibility Principle: each component/page encapsulates its template, styles, and logic.
• Build‐time separation: dev (ng serve) vs. prod (ng build) environments.
Final checklist
• All major components (Dev, Build, Host, Browser, AppModule, Router, Components, Assets).
• Call out Angular‐specific tech: TypeScript, Webpack, Angular CLI, Angular Router.