karthikeyan7333/swiggy-clone

Purpose and Delivery Model

This is a static, browser-rendered landing page modeled around Swiggy food delivery. It has no application backend, build system, package manifest, or README-defined runtime. A web server or direct file opening serves the page and its local assets.

Primary entry point:

• index.html

Page Composition

index.html defines the document structure, content, navigation, promotional areas, food/category imagery, and app-download calls to action. It is the control point for stylesheet and asset references and is expected to be rendered entirely by the browser.

Key paths:

• index.html

• swiggy.css

• images/swiggy_logo_white.avif

Custom Visual Layer

The repository’s product-specific presentation is concentrated in swiggy.css. This stylesheet likely supplies page layout, Swiggy-branded colors, hero sections, responsive styling, and overrides/additions beyond framework defaults.

Key paths:

• swiggy.css

• index.html

Bootstrap UI Foundation

A checked-in Bootstrap 5.3.8 distribution provides CSS layout/utilities and optional interactive browser components. The site can use Bootstrap’s grid and component classes from the locally served distribution; JavaScript behavior, if referenced by the page, comes from the bundled Bootstrap runtime.

Key paths:

• bootstrap-5.3.8-dist/css/bootstrap.css

• bootstrap-5.3.8-dist/js/bootstrap.bundle.js

• bootstrap-5.3.8-dist/bootstrap.html

Static Asset Boundary

All visual content is local and prepackaged. AVIF files provide food imagery, banners, logos, and mobile-store badges, keeping page rendering independent of a CMS, image API, or third-party CDN.

Key paths:

• images/App_download_banner.avif

• images/Sushi_replace.avif

• images/icon-AppStore_lg30tv.avif

Runtime Flow

On navigation to index.html, the browser loads linked Bootstrap and custom CSS, resolves local AVIF image references, creates the page DOM, and optionally initializes Bootstrap JavaScript components. There is no indicated data-fetching, authentication, persistence, server-side rendering, or external service integration.

Supporting Framework Examples

The Bootstrap directory includes framework example/demo pages and alternate CSS/JS builds. These are vendor artifacts rather than the product’s primary execution path; the application-facing page remains the repository-root index.html.

Key paths:

• bootstrap-5.3.8-dist/cards.html

• bootstrap-5.3.8-dist/js/bootstrap.js

• bootstrap-5.3.8-dist/css/bootstrap-grid.css