How yashhhyb/frontend-task works
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 index.html · script.js script.js · style.css style.css · images images/
Components 7
Client site
Static browser-delivered landing page for the exhibition
- Browser · Runs the static page and all client-side behavior
- index.html · Main HTML document and application entry point
index.html - style.css · Controls layout, theme, and visual presentation
style.css - script.js · Handles page interactivity and user-facing actions
script.js - Event content · Embedded landing-page copy for the exhibition, schools, and registration prompts
- Registration · Browser-side or externally linked path for parent registration
Content assets
Media and page content used by the front-end
- images/ · Visual assets referenced by the page
images
Connections 10
- 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