santhoshclx/personalportfolio

Purpose and runtime

This repository is a static personal portfolio site for presenting resume content, projects, and technical blogs. It runs entirely in the browser: HTML, CSS, and vanilla JavaScript, with no backend, build system, database, or server-side runtime. It is deployable to any static host.

Primary entry point: index.html.

Application shell and content sections

index.html is the portfolio shell and canonical source for the About, Resume, Projects, Blog, and Contact sections. It contains the navigation targets and links that connect portfolio cards to detail documents.

Key path:

• index.html

Client-side interaction and navigation

The browser-side controller in assets/js/script.js implements responsive navigation, section/view transitions, dynamic project/blog loading via loadProjectContent(), and copy-to-clipboard behavior for embedded code examples. This is the main control boundary between the persistent portfolio shell and fetched detail content.

Key paths:

• assets/js/script.js

• index.html

Styling and responsive presentation

A single global stylesheet defines theme variables, layout, responsive breakpoints, animations, component styling, and code/content presentation. CSS custom properties provide the site’s visual theming boundary.

Key paths:

• assets/css/style.css

• assets/images

Dynamically loaded project content

Project detail pages are standalone HTML fragments/documents retrieved by the client script and integrated into the portfolio experience without a full-page navigation. Existing projects span DevOps, ML, regex, and the portfolio itself.

Key paths:

• projects/AWSCodePipelineCICD.html

• projects/LinearRegressionFromSCRATCH.html

• projects/PatternMatchingRegEx.html

• projects/PersonalPortfolioWebsite.html

Blog content pipeline

Technical posts are static HTML documents under blogs/. Navigation from the main shell selects a post; the JavaScript content loader fetches and displays it in the portfolio interface. Blog pages may contain code blocks that participate in the shared clipboard interaction.

Key paths:

• blogs/RegularExpressionsGuide.html

• blogs/AWSCodePipeline.html

• blogs/AWSCloudWatchAgent.html

• blogs/AWSSystemsManager.html

External dependencies and delivery

The site relies on browser-native APIs, notably fetch for dynamic content and the Clipboard API for code copying. External presentation services include Google Fonts (Poppins) and Ionicons. Assets are served as static files; local development can use any static HTTP server. GitHub Actions contains a static-site workflow, indicating CI/static validation or deployment automation.

Key paths:

• .github/workflows/static.yml

• assets/css/style.css

• assets/js/script.js