manoharsamvel24/portfolio

Purpose and Entry Point

This repository is a static personal portfolio site. It is served directly from index.html, with browser-side behavior in script.js and presentation in style.css. No backend, build system, application server, or package-managed runtime is present.

Document Shell and Content

index.html is the primary composition boundary: it defines the portfolio’s page structure, content sections, asset references, and links. Browser loading begins here and delegates styling and interaction to adjacent root-level files:

• index.html

• style.css

• script.js

Presentation Layer

style.css owns the visual system and responsive layout for the static document. It is consumed directly by the browser, rather than generated from a preprocessing or component pipeline.

• style.css

• index.html

Client-Side Interaction

script.js provides any dynamic behavior after document load, such as navigation, UI state, animations, or DOM event handling. Its boundary is the browser DOM defined in index.html; it has no indicated API or server integration.

• script.js

• index.html

Static Asset Boundary

Visual resources are stored under assets/icons and are referenced by page markup and/or CSS. Assets are deployed with the site as static files.

• assets

• assets/icons

• index.html

Deployment and Automation

GitHub Actions contains a static-site-oriented workflow, likely responsible for validation or deployment automation. The workflow is the repository’s only visible infrastructure integration and runs in GitHub-hosted CI rather than application runtime code.

• .github/workflows/static.yml

Runtime and Control Flow

A browser requests index.html, then loads linked CSS, JavaScript, and icon assets. CSS renders the document; JavaScript attaches behavior to existing DOM elements. Repository changes can trigger the GitHub Actions static workflow, after which the generated—or directly served—static files are deployable without a backend service.