How yuvrajsinh5252/website works
Main Components
• Pages & Routing:
• The src/app directory is central. It houses pages for About, Blog (with dynamic [slug] routing), Projects, and the base homepage (page.tsx). This clearly represents the routing and view layer.
• UI Components & Effects:
• Under src/components, there are subdirectories for navbar, themes, about, blog, cursor, effects, and ui. These are reusable components that build up the UI and offer interactive effects (typewriter, sparkles, animated-post, etc.).
• Content and Data:
• The src/content directory (with MDX blog posts) and src/data (project details and social links) are used for dynamic content population.
• Library and Utilities:
• The src/lib folder contains helper functions for blog processing and utilities, indicating business logic separation.
• Core Configurations:
• The presence of configuration files (next.config.ts, tailwind.config.ts, postcss.config.mjs, tsconfig.json, etc.) shows reliance on tools and frameworks to structure the build, styling, and type-checking.
Out Relationships & Interactions
• Frontend/Pages Layer:
• UI Components Layer:
• Content/Data Layer:
• Library/Utilities Layer:
• “lib” module which offers helper functions and business logic. Indicate how these utilities are used by the components and pages to handle tasks like blog data fetching.
• Configuration & Styling:
Architectural Patterns & Design Principles
• Next.js/React Architecture:
• Component-based design typical of React with reusable UI modules.
• Separation of Concerns:
• Dynamic Routing & Content Injection:
• The use of MDX for blog posts and dynamic [slug] routes indicates content-driven page generation.
• Utilization of Third-Party Tools:
• Technologies like Tailwind CSS, TypeScript, ESLint, and PostCSS should be noted as key supporting frameworks.