How brubribeiro/projeto-bytebank-grupo-30 works
Project type and purpose
• From the file tree and the presence of angular.json, src/app, server.ts, and app.module.server.ts, it’s clear this is an Angular single-page application (SPA) set up for server-side rendering (Angular Universal).
• The README title “projeto-bytebank-grupo-30” suggests it’s a banking dashboard POC: home pages, dashboards, transaction forms, balance and extract views.
File structure
• Top‐level files:
• angular.json, tsconfig*.json, package.json → Angular CLI configuration and dependencies
• server.ts, main.server.ts → Node entrypoints for server‐side rendering
• README.md, .github/workflows/blank.yml → CI setup in GitHub Actions
• src/app: broken out into two feature areas:
• home (header, content, footer, overall home component)
• dashboard (balance, extract, new-transaction form with sub-components, menu, header)
• src/app/app-routing.module.ts and app.module.ts / app.module.server.ts define module imports and route setup.
• src/styles.css, custom-theme.scss for theming.
README
• We infer technology stack: Angular 14+ (TypeScript), Angular Universal (SSR), Node.js (server.ts), GitHub Actions for CI/CD.
Details
• Layer: CI/CD pipeline, hosting, SSR server, SPA runtime, external API
• Drill into the Angular folder structure: feature modules and their sub-components
• Routing module as the nexus of navigation
• Which files bootstrap which part (main.ts for client, main.server.ts for server)