How silascunha97/passaro-urbano works
Project type and purpose
• This is an Angular single-page application with server-side rendering (SSR) enabled via Angular Universal.
• Purpose: A client-facing web app (“PassaroUrbano”) that displays “ofertas” (offers) and static pages (restaurantes, diversão), reading data from a JSON “banco-de-dados.json” and serving both client and server bundles.
File structure
• Top-level build/config files: angular.json, tsconfig*.json, package.json
• “public/” – static assets and JSON database
• “src/server.ts”, “src/main.server.ts”, “src/app/app.module.server.ts”, “src/app/app.routes.server.ts” – Node.js entrypoint and server module for SSR
• “src/main.ts” – client bootstrap
• “src/app/” – Angular modules, routing, components, services, API adapters, interfaces
• “src/app/components/ui” – UI component hierarchy (buttons, pages, header, footer)
• “src/app/components/service” – business logic (OfertasService)
• “src/app/components/api” – HTTP wrappers (app.api.ts)
README for additional insights
• Standard Angular CLI project, with ng serve, ng build, ng test, ng e2e
• No custom architecture docs, so we rely on file structure to infer SSR, service layers, UI hierarchy.
Elements
• HTTP request/response flow
• Data requests from service to JSON file
• Client hydration sequence