How dibendu-saha/my-portfolio-tw works
Main Components
• Frontend UI: The core of the project is the client-side interface built in React. This includes:
• The “src” directory that contains all the React components, such as “home”, “about”, “contact”, “menu”, “xp”, etc.
• The “src/common” folder that provides shared components and constants.
• Assets & Styling: Images and styles are kept under “src/assets” (with images separated in subdirectories) and multiple styling resources spread across “index.scss”, “App.scss”, and Tailwind’s configuration in “tailwind.config.js” and PostCSS configuration.
• Services & Utilities: The “src/services” directory holds API endpoint definitions, while utilities like image preloading are located in “src/utils”. This indicates separation for data fetching and reusable functions.
• Build & Configuration: Project-level configuration files (e.g., package.json, vite.config.ts, tsconfig files, .eslintrc.cjs, .prettierrc, azure-pipelines.yml, and GitHub workflow YAML files) signal CI/CD integration and coding standards.
Component Relationships and Interactions
• The UI components (e.g., Home, About, Contact, Menu) interact with shared common components and may call functionality from “services” for any dynamic data.
• The “common” components provide reusable UI elements that appear across different parts of the UI.
• Assets (images and styles) support the UI components, ensuring a consistent look and feel.
• The service layer illustrates how the frontend might interact with external APIs or data endpoints, even if the current project’s functionalities might be mostly static.
• The build pipeline is represented by files for GitHub workflows and Azure Pipelines, highlighting automated deployment and testing stages.
Important Architectural Patterns & Design Principles
• Component-Based Architecture: The React code is organized into specific feature folders (home, about, contact, etc.) and leverages common components for shared functionality.
• Separation of Concerns: Different directories (assets, components, services, utils) clarify the responsibilities of each part of the application.
• Configuration Management: The multiple configuration files for linters, formatters, and build tools demonstrate a focus on maintainability and code quality.
• CI/CD Integration: The presence of GitHub workflows and Azure pipelines indicates automated builds, tests, and deployments.
Relevant Technologies and Tools
• React and TypeScript for building the UI.
• Vite as the build tool/bundler.
• Tailwind CSS (with instructions to install specific plugins and VS Code extensions) and PostCSS for styling.
• ESLint, Prettier (with the Tailwind plugin), and associated configuration files for code quality.
• Additional deployment and CI/CD configurations which support seamless integration with AWS infrastructure (as mentioned in the README).