abhishek-sharma2028/policy_ease_website

Purpose and Runtime

This is a Vite-served React 19 single-page “Policy Translator Platform.” It presents a fixed, curated catalogue of Indian policies and welfare schemes in simplified language, organized by audience category. The app is entirely client-side: no backend, authentication, search service, or AI engine currently exists.

Primary browser entry points are index.html, src/main.jsx, and src/App.jsx. Vite configuration is in vite.config.js.

Application Composition

src/App.jsx is the page-level orchestrator, assembling the landing-page sections and managing the user journey from discovery to policy details. Shared presentation primitives live in:

• src/components/Header.jsx

• src/components/Card.jsx

• src/components/Button.jsx

Global styling and design tokens establish the visual system, including the stated glassmorphism-oriented theme:

• src/index.css

• src/styles/variables.css

Curated Policy Data Boundary

The application’s authoritative content is static frontend data rather than API-delivered records. src/data/policies.js defines the verified policy catalogue, likely including display copy, categories, eligibility information, and links to supporting assets. src/data/categories.js defines the target user groups used to segment discovery.

This is the principal content boundary: changing, adding, or validating policies requires updating these source-controlled datasets and corresponding static media.

• src/data/policies.js

• src/data/categories.js

Discovery and Category Flow

Users begin at the hero and navigate into category-based exploration rather than free-text search. Categories renders the audience/category choices; selection drives the policy-list view, which filters or scopes the curated policy records.

• src/sections/Hero.jsx

• src/sections/Categories.jsx

• src/sections/PolicyList.jsx

The HowItWorks and about-oriented sections support explanation and trust but are not data-processing layers:

• src/sections/HowItWorks.jsx

• src/sections/AboutDetail.jsx

Policy Detail and Eligibility Flow

A selected policy is rendered through PolicyDetail, which is the main policy-information endpoint in the UI. It presents the simplified explanation and can expose supporting PDF/audio resources from the static asset boundary.

EligibilityChecker is the user-assessment stage: it collects or evaluates user-facing eligibility criteria against the selected policy’s static metadata. Any eligibility result is browser-local and deterministic; no external government verification or service integration is present.

• src/sections/PolicyDetail.jsx

• src/sections/EligibilityChecker.jsx

• src/data/policies.js

Static Documents and Audio Assets

Policy source/support material is bundled as public files served directly by Vite. The canonical web-consumed assets are under public/, including MP3 explainers and selected PDFs. The root-level audio files/ and pdfs/ directories appear to retain broader or source copies.

• public/audio/

• public/pdfs/

• public/hero-bg.mp4

Asset paths referenced by policy data must remain aligned with these public filenames; there is no media API, storage service, or content delivery integration visible.

Infrastructure and Extension Boundaries

Execution is Node/npm-based with Vite development/build tooling and React rendering. ESLint is present for code quality, but there are no deployed infrastructure definitions, server routes, databases, or third-party APIs in the repository.

The planned AI recommendation, multilingual support, and personalization would require introducing a new service/data boundary rather than extending the current static-data-only flow.