johann-09/coder-entregable-clase4

Purpose and delivery model

This is a static Spanish-language personal/professional website. It has no application source, backend, package manifest, or README-defined build process; deployment consists of serving the HTML, CSS, and image assets directly.

Entry points and site topology

index.html is the primary landing-page entry point. The rest of the site is split into independently served HTML documents under pages/:

• pages/sobre-mi.html — profile/about content

• pages/servicios.html — services

• pages/proyectos.html — projects

• pages/contactos.html — contact information

• pages/preguntas.html — questions/FAQ-style content

• pages/temas.html — topics

Navigation and inter-page behavior are expected to be standard browser links between these documents rather than client-side routing.

Presentation layer

A shared stylesheet at css/style.css is the central visual-system boundary. Each HTML page likely references this common asset, making it the primary place for shared layout, typography, responsive behavior, navigation styling, and page-level visual consistency.

Relevant paths:

• css/style.css

• index.html

• pages/servicios.html

Content architecture

Content is page-centric and authored directly in HTML rather than sourced from a CMS, API, or data layer. Each page owns its document structure and copy, so changes to a section’s content or markup occur in its respective file.

Relevant paths:

• pages/proyectos.html

• pages/preguntas.html

• pages/temas.html

Asset boundary

img/ is the repository’s static media boundary. HTML pages and the shared stylesheet may reference images by relative path. Asset naming, optimization, and relative URL correctness are important because there is no bundler or asset pipeline visible in the repository.

Relevant paths:

• img

• index.html

• css/style.css

Runtime and infrastructure

The runtime is a browser plus any static-file host (for example, GitHub Pages, Netlify static hosting, or a conventional web server). No server-side runtime, database, authentication system, API integration, or third-party service is evidenced by the supplied tree. The key deployment concern is preserving directory structure so root and pages/ documents resolve CSS, image, and cross-page links correctly.