sofianester/portfolio

Purpose and Delivery Model

This repository is a static personal portfolio for Sofiane Benslimane, presenting design/technology work, external project links, contact channels, and downloadable resumes. It is deployed as plain web assets: no backend, build service, database, or server-side application is represented.

Core entry points:

• index.html — primary portfolio landing page.

• project.html — project-detail presentation page.

• terms.html and privacy.html — legal-content pages.

Page and Navigation Layer

HTML pages define the site’s content, navigation, project presentation, and outbound links. The browser loads each page directly; navigation is conventional document navigation rather than client-side routing.

Relevant paths:

• index.html

• project.html

• privacy.html

Primary Content Flow

The primary user flow is: open index.html → browse profile/work sections → follow social, email, Figma, or project links → optionally download a resume PDF. Project-specific information is separated into project.html, while legal links terminate at static policy pages.

Resume artifacts are directly served files:

• Sofiane-Benslimane-2026.pdf

• Sofiane-Benslimane-07-2026.pdf

• Sofiane-Benslimane-2026-old.pdf

Styling Architecture

Two styling families coexist:

1. The documented portfolio stack uses Bootstrap, Font Awesome, and site-specific CSS.

2. An HTML5 UP/Miniport-derived asset set includes compiled CSS and Sass sources.

The browser consumes compiled CSS; Sass is source-level maintenance material and is not an in-browser runtime.

Relevant paths:

• css/bootstrap.css

• css/fontawesome-all.css

• css/styles.css

• assets/css/main.css

• assets/sass/main.scss

Client-Side Behavior

JavaScript is entirely browser-side and supports presentation/interaction behavior. There is no evidence of API calls, authentication, persistence, or application state management. The README identifies jQuery as part of the template/runtime stack; the file tree exposes site scripts but not a separately listed jQuery distribution.

Relevant paths:

• js/scripts.js

• assets/js/main.js

• assets/js/util.js

Assets and External Boundaries

Static images, icon fonts, and CSS image resources are served locally. Font Awesome webfonts support icon rendering. External boundaries are outbound destinations such as LinkedIn, email, and Figma rather than integrated services.

Relevant paths:

• images

• webfonts/fa-solid-900.eot

• assets/webfonts/fa-brands-400.eot

• assets/css/images

Operational Characteristics

The repository can be hosted on any static-file host or web server. Its key runtime boundary is the browser: HTML composes pages, CSS handles responsive layout, JavaScript enhances interactions, and PDFs/assets are downloaded or rendered directly. Changes should preserve relative asset references across the top-level css/, js/, images/, and template-derived assets/ trees.