How jaitensahu/project-dr.pathlab works
Project Type and Purpose
• This is a static frontend web application: a faithful clone of the Dr. Lal PathLabs website.
• Purpose: Client‐side UI only, built with HTML, CSS (Tailwind), and JavaScript libraries. Hosted as static assets (e.g., on GitHub Pages).
Main Components
a. Developer Workstation
• Source directories for each section (About_us, Book_a_test, Bussiness, Contact_us, Doctors, Investors, Patients) under /src.
• Configuration files: tailwind.config.js, package.json & package-lock.json.
• Node.js tooling (Tailwind CLI, postcss, local dev server).
b. Build Pipeline
• Tailwind CSS processing: /src/input.css → build → /dist/output.css.
• Asset bundling: Copying HTML, JS libraries (Flickity, AOS, FontAwesome), images into /dist.
c. Static Hosting
• GitHub Pages or any CDN.
• Destination: /dist folders for each section, plus top‐level Patients/index.html.
d. Client Browser
• Loads HTML, CSS, JS.
• Renders UI, executes Flickity carousels, AOS animations.
e. External Libraries/CDNs
• Flickity (local flickity.pkgd.js or CDN).
• AOS (Animation on Scroll).
Relationships and Data Flow
• Developer Workstation → Build Pipeline:
• Node.js reads tailwind.config.js, processes /src/input.css → /dist/output.css.
• Copy HTML templates and JS libs into /dist.
• Build Pipeline → Static Hosting:
• Deploy /dist folders for each section to GitHub Pages.
• Client Browser ↔ Static Hosting:
• Browser sends HTTP(S) requests for HTML, CSS, JS, images.
• Browser renders pages, interacts with UI libraries.
• Client Browser ← External CDNs (optional):
• If using CDN links for AOS or Font Awesome.
Architectural Patterns & Design Principles
• Modular Multi‐Page Layout: Each site section is a self‐contained module.
• Static Site Deployment: No runtime server logic; purely client‐side.
• Asset Pipeline: Source files → build → optimized assets.
• Separation of Concerns:
• HTML for structure,
• Tailwind CSS for styling,
• JS libraries for interactive behaviors.