How nailuj1992/nailuj-portfolio works
Project Type and Purpose
• Project Type: This is a frontend portfolio website built with Angular (version 17.1.2) with some server-side configuration (server.ts, server.js, main.server.ts) that may be involved in server-side rendering (Angular Universal) or other API functions.
• Purpose: To showcase the portfolio of Julián González Prieto (alias “Náiluj”), illustrating separate pages for home, about, contact, portfolio, experience, and studies—all designed to look visually appealing. The deployment is on Vercel.
File Structure
• Top-Level Files: Notice configuration files such as angular.json, tsconfig files, package.json, and deployment-related files (.vercel/ project.json, .editorconfig, .gitignore).
• Directories:
• /src: The application’s source which includes:
▪ /app: Contains Angular components, configuration, routing (app.routes.ts), and service files.
▪ /components: Houses page-specific components (e.g., home, about, contact, portfolio, etc.).
▪ /elements: Contains shared UI elements (footer, menu, image-slider, scroll-to-top, separator).
▪ /model: Provides data transfer objects (DTOs) for language settings and sending mail.
▪ /services: Contains the mail service responsible for handling contact form email functionality.
▪ /assets: Holds images and some design files.
• Server Files: Files like server.ts, server.js, main.server.ts indicating server-side elements (possibly for SSR or API endpoints).
• Environment Configuration: /src/environments for handling environment-specific variables.
• Architectural Clues:
• Angular’s component-based design is evident.
• There is a clear separation between UI pages (in components) and shared elements (in elements).
• Service and model layers support backend-like functionality (e.g., mail service via DTOs).
Examining the README
• The README confirms the project is a portfolio application, explains who the developer is, and notes that it’s deployed on Vercel.
• It subtly hints at an emphasis on UI/UX ("good and pretty manner"), aligning with the detailed component structure under src/app.
a. Main Components to Represent:
• Client-Side (Angular App) Layer:
• App Module: Central container coordinating routes (app.routes.ts), configurations (app.config.ts and app.config.server.ts).
• Page Components: Home, About, Contact, Portfolio, Experience, Studies.
• Shared UI Elements: Footer, Menu, Image Slider, Scroll-to-top, Separator.
• Services: Mail Service (with DTOs like send-mail-dto.ts) which supports the Contact page.
• Model Layer: DTO definitions for language settings and email payload.
• Assets & Themes: Custom SCSS theme (custom-theme.scss) and static assets (images, svg).
• Server-Side Layer:
• Server Scripts: server.ts and server.js, main.server.ts that may be configuring server-side rendering or API endpoints.
• Environment Configurations: Handling different environments using configuration files in /src/environments.
• Deployment and Configuration:
• Build and Configuration Files: angular.json, tsconfig*.json, package.json, and Vercel configuration (.vercel directory).
b. Relationships and Interactions:
• Data/Control Flow:
• The Angular router (app.routes.ts) directs users to various page components.
• Services (like mail.service) facilitate asynchronous communication (e.g., sending email data).
• The server-side components act as the backend entry point for either server-side rendering or to support API operations.
• The components depend on shared services and DTO models for consistency in data handling.
• External Integration:
• Vercel Deployment acts as the external host, ensuring continuous deployment through the provided config files.
c. Key Architectural Patterns and Technologies:
• Component-Based Architecture: Each feature (page or UI element) is encapsulated as its own Angular component.
• Service-Oriented/Dependency Injection: Angular services handle business logic (mail service) and interact with DTOs.
• Environment-Based Configuration: Managed via /src/environments.
• Server-Side Role (if applicable): Representing SSR or a simple Node.js-based server (via server.ts/server.js).