rmadheswaran/fluxa_website

Purpose and entry points

This is a static marketing/legal website with no README, backend, package manifest, or build system visible. The primary public entry point is index.html; alternate or legacy landing-page variants exist in index-old.html and index_1.html.

Page layer

HTML documents define the site’s navigable content and likely share common navigation/footer patterns:

• index.html

• privacy-policy.html

• refund-policy.html

Legal content is separated into dedicated static routes, including terms-conditions.html. Hosting only needs to serve files and preserve these HTML paths.

Styling architecture

The presentation layer is CSS-based and split between general site styling and legal-page styling:

• css/style.css

• css/legal.css

• css/styles_old.css

css/style.css is the likely current global stylesheet. css/legal.css isolates policy/terms formatting, while css/styles_old.css likely supports the legacy page variant and should be treated as compatibility/alternate-design surface.

Client-side behavior

Browser-side interactivity is centralized in:

• js/script.js

There are no visible framework bundles, server handlers, API clients, or dependency metadata. JavaScript behavior is therefore expected to operate directly on page DOM elements and be loaded by individual HTML pages.

Static assets boundary

Non-code media is expected under:

• assets

HTML references assets, CSS, and JavaScript through static relative URLs. Any deployment, CDN, or asset optimization process must retain this directory structure or update those references consistently.

Runtime and infrastructure

The material runtime is a standard web browser served by static-file hosting (for example, a web server, object storage site host, or CDN). No application server, database, authentication service, external API integration, or build/deployment configuration is present in the repository tree.

Primary flow

A visitor requests an HTML route such as index.html; the browser loads referenced CSS from css/, scripts from js/, and media from assets/. Navigation to legal pages loads separate standalone HTML documents styled by the shared or legal-specific CSS. The main architectural boundary is between static content/layout (HTML), presentation (CSS), direct browser behavior (JavaScript), and static media assets.