How m-a-n-i-k/manik-dingra works
Project Overview
• This is a front-end portfolio website built with Next.js 15 using the App Router, TypeScript, and Tailwind CSS. Its primary purpose is to showcase a personal portfolio with smooth animations, dynamic content, and interactive UI components.
• Key technologies include Next.js (for server-side rendering and routing), Tailwind CSS (for styling), and Lenis Smooth Scroll (for enhanced scrolling effects).
Main Components
a. App Directory (Next.js App Router):
• Contains crucial files such as layout.tsx and page.tsx that define the overall application structure and routing.
• Includes global styles (globals.css), and even configuration pages like robots.ts and sitemap.ts to manage SEO specifics.
b. Components:
• Houses individual UI modules like hero-section, projects-section, about-section, skills-section, experience-section, footer, navbar, etc.
• These components are organized functionally, each responsible for a distinct segment of the portfolio (e.g., landing, projects showcase, skills grid).
c. Public Folder:
• Stores static assets like images or project assets used in the project (e.g., under public/projects) and the site manifest.
d. Lib:
• Contains the integration for the Lenis Smooth Scroll functionality, a key component that adds smooth scroll effects to the portfolio.
e. Configuration Files:
• Files like next.config.ts, tailwind.config.ts, tsconfig.json, and ESLint and PostCSS configuration files determine the project's build and style behavior.
Defining Relationships and Interactions
• The App directory acts as the entry point: the layout component establishes the main structure, while page.tsx acts as the initial route.
• The main container component (in Components) is central, aggregating and orchestrating the display of other visual sections (hero, projects, about, skills, experience, etc.).
• Components interact with each other via React props where data and UI state are passed among them. For example, the projects-section leverages project-card components, and the smooth scroll library (from Lib) ties into the main-container for scrolling behaviors.
• Static assets in the Public folder are referenced by components to render images and project details.
• Configuration files support the entire structure: Next.js handles routing and server-side behavior, Tailwind config customizes the design system, and the TS and ESLint configs maintain code quality.
Architectural Patterns & Design Principles
• Component-Based Architecture: The design embraces React’s component paradigm, where each UI part is isolated and reusable.
• Separation of Concerns: By dividing the project into distinct directories (app, components, lib, public), the project maintains clear boundaries for concerns like routing/layout, UI components, third-party integrations, and static assets.
• Configuration/Convention over Code: Key config files ensure consistent theming and behavior across the project.