How renechm/angular works
Project type and purpose
• From the file tree and README, this is a single-page web application built with Angular CLI v6.0.8.
• It’s a “Portafolio” front-end app: no separate backend service, all data is stored under src/assets (JSON + static images).
• The docs folder appears to hold the production build (HTML/CSS/JS) ready for static hosting (e.g., GitHub Pages).
File structure
• Top-level config:
• angular.json, tsconfig*.json, tslint.json — Angular CLI and TypeScript tooling
• package.json / package-lock.json — npm dependencies and scripts
• Source code under src/:
• src/app/ — Angular code organized by modules, pages, shared components, services, and interfaces
• src/assets/ — Static assets (CSS frameworks, fonts, JSON data, product images, custom JS)
• src/environments/ — Environment configurations (dev vs. prod)
• End-to-end tests under e2e/, unit tests co-located under src/app (spec.ts).
README for additional insights
• Standard Angular CLI workflows: serve, build, test, e2e.
• No mention of external APIs or microservices—confirming a purely client-side app.