diegomonterocrc/diegomonterocrc

Purpose and Delivery Model

This repository is a static personal portfolio/CV site for Luis Diego Montero Vargas. It presents professional profile content, skills, projects, social/contact links, and downloadable CVs. There is no backend, database, build system, or application API indicated.

Entry Point and Browser Runtime

index.html is the site entry point loaded directly by a browser. It defines the document structure, portfolio sections, links, and references to local assets, CSS, and JavaScript. The runtime boundary is the client browser; deployment can be any static-file host.

Paths: index.html, css/style.css, js/script.js

Presentation Layer

Styling is centralized in css/style.css, which controls layout, visual hierarchy, responsive behavior, and presentation of the HTML content. index.html remains the content and semantic structure boundary, while CSS owns visual rendering.

Paths: index.html, css/style.css

Client Interaction Layer

js/script.js supplies browser-side behavior for the otherwise static page, such as navigation or UI interactions implemented by the portfolio. It operates on DOM elements emitted by index.html; it should not be treated as a service or data-processing layer.

Paths: js/script.js, index.html

Content and Portfolio Flow

Visitors enter through index.html, consume profile and project information, then follow outbound actions: GitHub, LinkedIn, email, and the separately hosted Streamlit energy-prediction demo. The repository itself contains the presentation shell rather than the referenced analytics projects.

Paths: index.html, README.md

Downloadable and Visual Assets

Local binary assets support the site’s CV/download and visual content. The two PDFs provide English and Spanish CV variants; image and icon directories are intended for site-local visuals referenced by the page and styles.

Paths: assets/EN-Luis-Diego-Montero-CV.pdf, assets/SP-Luis-Diego-Montero-CV.pdf, assets/img

External Boundaries

The site links to external GitHub and LinkedIn profiles, uses mailto: for email initiation, and references a Streamlit-hosted visualization. The README additionally embeds externally served badge and GitHub-stat images, but those are repository documentation integrations rather than application infrastructure.

Paths: README.md, index.html