# yashhhyb/frontend-task architecture

> Architecture diagram of the GitHub repository yashhhyb/frontend-task, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-20). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/yashhhyb/frontend-task
- Repository: https://github.com/yashhhyb/frontend-task

## Overview

1. **Project type**
   - This is a **static marketing/landing page** for the “Premier Schools Exhibition” in Gurugram 2025.
   - The repository has no backend code, build pipeline, package manifest, or server runtime.

2. **Primary entry point**
   - `index.html` is the application entry point.
   - The page is meant to be opened directly in a browser, so the browser is both the renderer and the runtime.

3. **Presentation layer**
   - `style.css` controls the page’s visual design and layout.
   - The architecture is front-end only: HTML defines structure, CSS defines presentation, and JavaScript handles behavior.

4. **Client-side behavior**
   - `script.js` contains the interactive logic for the landing page.
   - Based on the README, this likely supports user-facing interactions around event information and parent registration, rather than any server-driven workflow.

5. **Content/data layer**
   - The content appears to be mostly static: exhibition details, participating schools, and registration prompts.
   - There is no visible data service, CMS, or database; content is embedded in the front-end files.

6. **Media/assets**
   - The `images/` directory stores visual assets used by the page.
   - These assets are part of the browser-delivered presentation layer and are referenced from the HTML/CSS.

7. **User flow**
   - A visitor opens `index.html` in a browser.
   - The page displays event information and school listings.
   - The user is guided toward a registration action for the exhibition.

8. **Registration boundary**
   - The README says the site “allows parents to register for the event,” but there is no evidence of a backend service in the repo.
   - From an architecture perspective, registration is either handled entirely client-side, via an external form/service, or is a placeholder for future integration.

9. **Execution model**
   - Everything runs in the browser after static file loading.
   - There are no asynchronous dependencies visible in the repository tree, so the app is likely lightweight and self-contained.

10. **Development/tooling files**
   - `.hintrc` suggests use of a front-end linting or accessibility/performance hinting tool.
   - `.vscode/` contains editor settings for local development and does not affect runtime architecture.

11. **Deployment shape**
   - The site can be deployed as plain static hosting: any web server, object storage static site, or even local file opening.
   - There are no infrastructure dependencies to diagram beyond file hosting/CDN if used externally.

12. **Architectural summary**
   - The repository is a **single-page static front-end** with three main concerns:
     - structure in `index.html`
     - styling in `style.css`
     - interactivity in `script.js`
   - Images provide supporting media, and all user interaction happens in the browser.

Main entry points: [`index.html`](https://github.com/yashhhyb/frontend-task/blob/main/index.html) (index.html), [`script.js`](https://github.com/yashhhyb/frontend-task/blob/main/script.js) (script.js), [`style.css`](https://github.com/yashhhyb/frontend-task/blob/main/style.css) (style.css), [`images`](https://github.com/yashhhyb/frontend-task/tree/main/images) (images/)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_app["Client site"]
  node_browser(("Browser<br/>runtime"))
  node_index_html["index.html<br/>entry page<br/>[index.html]"]
  node_style_css["style.css<br/>stylesheet<br/>[style.css]"]
  node_script_js["script.js<br/>client logic<br/>[script.js]"]
  node_exhibition_content["Event content<br/>static content"]
  node_registration_flow["Registration<br/>user action"]
end

subgraph group_content["Content assets"]
  node_images_dir[("images/<br/>media assets")]
end

node_browser -->|"loads"| node_index_html
node_index_html -->|"uses"| node_style_css
node_index_html -->|"uses"| node_script_js
node_index_html -->|"references"| node_images_dir
node_index_html -->|"contains"| node_exhibition_content
node_script_js -->|"drives"| node_registration_flow
node_exhibition_content -->|"prompts"| node_registration_flow
node_browser -->|"applies"| node_style_css
node_browser -->|"executes"| node_script_js
node_browser -->|"renders"| node_images_dir

click node_index_html "https://github.com/yashhhyb/frontend-task/blob/main/index.html"
click node_style_css "https://github.com/yashhhyb/frontend-task/blob/main/style.css"
click node_script_js "https://github.com/yashhhyb/frontend-task/blob/main/script.js"
click node_images_dir "https://github.com/yashhhyb/frontend-task/tree/main/images"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_browser,node_index_html,node_style_css,node_script_js,node_exhibition_content,node_registration_flow toneBlue
class node_images_dir toneAmber
```

## Components

### Client site

Static browser-delivered landing page for the exhibition

- **Browser**: runtime · Runs the static page and all client-side behavior
- [index.html](https://github.com/yashhhyb/frontend-task/blob/main/index.html): entry page · Main HTML document and application entry point · `index.html`
- [style.css](https://github.com/yashhhyb/frontend-task/blob/main/style.css): stylesheet · Controls layout, theme, and visual presentation · `style.css`
- [script.js](https://github.com/yashhhyb/frontend-task/blob/main/script.js): client logic · Handles page interactivity and user-facing actions · `script.js`
- **Event content**: static content · Embedded landing-page copy for the exhibition, schools, and registration prompts
- **Registration**: user action · Browser-side or externally linked path for parent registration

### Content assets

Media and page content used by the front-end

- [images/](https://github.com/yashhhyb/frontend-task/tree/main/images): media assets · Visual assets referenced by the page · `images`

## Connections

- Browser → index.html: loads · The browser opens the static entry page
- index.html → style.css: uses · HTML pulls in presentation rules
- index.html → script.js: uses · HTML loads client-side behavior
- index.html → images/: references · Page markup and styles reference media assets
- index.html → Event content: contains · The page embeds the landing content directly
- script.js → Registration: drives · Interactive logic guides the user toward registration
- Event content → Registration: prompts · Event details and calls to action lead into registration
- Browser → style.css: applies · The browser renders the page using the stylesheet
- Browser → script.js: executes · Client-side code runs in the browser
- Browser → images/: renders · The browser displays image assets as part of the page
