How charingan/portfolio works
Project type and purpose
• This is a single-page application (SPA) built with Angular (v19).
• Its purpose is to serve as a personal portfolio website, with sections like Home, About, Skills, Projects, Art, and Contact.
File structure
Top-level files and folders:
• angular.json, tsconfig*.json, package.json – Angular build and TypeScript configuration
• src/ – application source code
– src/app/ – all Angular components and routing
– src/index.html, main.ts – application entry point and bootstrap
– src/styles.scss – global styles
• public/ – static assets (CV.pdf)
• README.md – Angular CLI instructions
Inside src/app/:
• app.config.ts – global configuration constants
• app.routes.ts – route definitions for the Angular Router
• app.component.* – the root component (shell)
• feature folders (about, art, contact, footer, header, home, project, skills) – each contains one component
README for additional insights
• No backend or external API is mentioned – this is a static, client-only site.
• Standard Angular CLI commands are used for serve, build, test.
Main components
a. User / Browser – the end user interacts through a web browser.
b. Static Web Server (e.g., Netlify, Firebase Hosting, GitHub Pages) – serves the compiled files from dist/.
c. Angular Application – runs in the browser and consists of:
• Bootstrap (main.ts → AppModule)
• AppComponent (shell)
• Router (app.routes.ts)
• Feature Components (AboutComponent, HomeComponent, etc.)
• Shared Components (HeaderComponent, FooterComponent)
• Global styles and assets (styles.scss, public/)
d. Build Pipeline – Angular CLI & Webpack that produces dist/ artifacts
Relationships and interactions
• The user makes HTTP requests to the static web server, which serves index.html and bundled JS/CSS.
• The browser loads the Angular runtime, bootstraps AppModule in main.ts.
• AppComponent initializes and the Angular Router picks a feature component based on the URL.
• Feature components may read from app.config.ts for any constants (e.g., profile data), load static assets from public/.
Architectural patterns & design principles
• Component-based architecture (each UI section is an isolated component)
• Separation of concerns:
• Routing logic in app.routes.ts
• Configuration in app.config.ts
• Presentation in .html/.scss files
• Single Responsibility: each Angular component has its own folder and resources.
Technologies/frameworks/libraries
• Angular framework (modules, components, router)
• TypeScript
• SCSS for styling
• Angular CLI (build, serve, test)
Elements
• Clear labels: “User”, “Browser”, “Static Host”, “Angular Runtime”, “AppModule”, “Feature Components”, “Assets”
• User → Browser (interaction)
• Browser → Static Host (HTTP GET /)
• Static Host → Browser (index.html + bundles)
• Bundles → Angular Runtime → AppModule → Components
• Rectangles for components/modules
• Parallelogram for config files
Final advice
• Don’t over-complicate: this is a single‐tier front-end app.
1. Presentation (Browser + UI components)
2. Application (Angular modules & router)
3. Deployment (Static host & build pipeline)
• Every folder and file category as a component or asset block so nothing is missed.