# elma-123/portfolio architecture

> Architecture diagram of the GitHub repository elma-123/portfolio, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-07-02). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/elma-123/portfolio
- Repository: https://github.com/elma-123/portfolio

## Overview

1. This repository is a **single-page static portfolio site**. There is no backend, database, or server-side application code in the tree; the entire experience runs in the browser and is suitable for static hosting such as GitHub Pages.

2. **`index.html` is the primary composition layer**. It likely defines the full page structure: navigation, hero, about/skills, projects, publications, certificates, and contact sections. The README indicates all content is embedded directly in this page rather than pulled from an API or CMS.

3. **`script.js` is the interaction layer**. Based on the README, it handles smooth scrolling, mobile menu behavior, active-section highlighting, scroll/animation effects, and the contact form integration with EmailJS. This script is the only dynamic runtime logic in the app.

4. **`styles.css` is the custom presentation layer**. It appears to hold site-specific styling such as glass morphism, gradients, hover states, custom scrollbar behavior, and animation tweaks that go beyond standard Tailwind utilities.

5. **Tailwind CSS is the main styling system**, with configuration in `tailwind.config.js` and `postcss.config.js`. This indicates a build step that compiles utility classes into the generated stylesheet in `dist/output.css`, which is the browser-facing CSS artifact.

6. **`dist/output.css` is the compiled CSS bundle**. It is the built output that combines Tailwind-generated utilities and likely any processed custom styles used by `index.html`. In architecture terms, this is the static presentation artifact consumed by the browser.

7. The **assets folder is content storage**, not application logic. In this repo it contains several PDF documents, including publications and project-related papers, which are likely linked from the portfolio as downloadable evidence of research, certifications, or writing.

8. The **contact flow is the only external service integration**. The README specifies EmailJS, so the browser sends form data directly to EmailJS rather than to a custom backend. That makes the contact form a client-to-third-party request path.

9. The **data model is mostly content-first and static**. Personal profile details, project descriptions, social links, and publication references are probably hardcoded in the HTML and/or script, making updates a manual content-editing task rather than a data ingestion pipeline.

10. The **main runtime boundary is the browser**. All navigation, animation, and responsiveness happen client-side; the browser loads `index.html`, reads styles from `dist/output.css` and `styles.css`, executes `script.js`, and serves linked documents from `assets/`.

11. From an architecture-diagram perspective, the repo is best drawn as:
   **static HTML shell + compiled CSS + custom JS interactions + static document assets + third-party EmailJS service**.
   There are no internal service tiers or persistent storage layers.

12. The overall design is optimized for **presentation and personal branding**, not data processing. The repo’s structure reflects a documentation-heavy portfolio where the primary concerns are layout, responsiveness, animation, and outbound links to external profiles and downloadable PDFs.

Main entry points: [`dist/output.css`](https://github.com/elma-123/portfolio/blob/main/dist/output.css) (Compiled CSS), [`index.html`](https://github.com/elma-123/portfolio/blob/main/index.html) (Home page), [`script.js`](https://github.com/elma-123/portfolio/blob/main/script.js) (Interactions), [`assets`](https://github.com/elma-123/portfolio/tree/main/assets) (PDF assets)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_frontend["Frontend"]
  node_index_html["Home page<br/>static html<br/>[index.html]"]
  node_script_js["Interactions<br/>client script<br/>[script.js]"]
  node_styles_css["Custom styles<br/>css source<br/>[styles.css]"]
end

subgraph group_build["Build"]
  node_tailwind_config["Tailwind config<br/>css config<br/>[tailwind.config.js]"]
  node_postcss_config["PostCSS config<br/>build config<br/>[postcss.config.js]"]
  node_dist_output_css["Compiled CSS<br/>build artifact<br/>[output.css]"]
end

subgraph group_content["Content"]
  node_assets_pdfs[("PDF assets<br/>static documents")]
end

subgraph group_external["External"]
  node_emailjs{{"EmailJS<br/>third-party service"}}
end

node_browser(("Browser<br/>runtime"))

node_browser -->|"loads"| node_index_html
node_browser -->|"applies"| node_dist_output_css
node_browser -->|"executes"| node_script_js
node_browser -->|"serves"| node_assets_pdfs
node_index_html -->|"links"| node_dist_output_css
node_index_html -->|"boots"| node_script_js
node_index_html -->|"references"| node_assets_pdfs
node_styles_css -.->|"builds into"| node_dist_output_css
node_tailwind_config -.->|"configures"| node_dist_output_css
node_postcss_config -.->|"processes"| node_dist_output_css
node_script_js -->|"submits form"| node_emailjs

click node_index_html "https://github.com/elma-123/portfolio/blob/main/index.html"
click node_script_js "https://github.com/elma-123/portfolio/blob/main/script.js"
click node_styles_css "https://github.com/elma-123/portfolio/blob/main/styles.css"
click node_tailwind_config "https://github.com/elma-123/portfolio/blob/main/tailwind.config.js"
click node_postcss_config "https://github.com/elma-123/portfolio/blob/main/postcss.config.js"
click node_dist_output_css "https://github.com/elma-123/portfolio/blob/main/dist/output.css"
click node_assets_pdfs "https://github.com/elma-123/portfolio/tree/main/assets"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_index_html,node_script_js,node_styles_css toneBlue
class node_tailwind_config,node_postcss_config,node_dist_output_css toneAmber
class node_assets_pdfs toneMint
class node_emailjs toneRose
class node_browser toneNeutral
```

## Components

### Frontend

Browser-facing page composition, behavior, and styling

- [Home page](https://github.com/elma-123/portfolio/blob/main/index.html): static html · Single-page portfolio composition and content sections · `index.html`
- [Interactions](https://github.com/elma-123/portfolio/blob/main/script.js): client script · Smooth scrolling, menu state, section highlighting, animations, and contact flow · `script.js`
- [Custom styles](https://github.com/elma-123/portfolio/blob/main/styles.css): css source · Portfolio-specific visual treatment and refinements · `styles.css`

### Build

CSS tooling and generated output

- [Tailwind config](https://github.com/elma-123/portfolio/blob/main/tailwind.config.js): css config · Tailwind build configuration · `tailwind.config.js`
- [PostCSS config](https://github.com/elma-123/portfolio/blob/main/postcss.config.js): build config · PostCSS pipeline configuration · `postcss.config.js`
- [Compiled CSS](https://github.com/elma-123/portfolio/blob/main/dist/output.css): build artifact · Generated stylesheet consumed by the browser · `dist/output.css`

### Content

Static downloadable portfolio documents

- [PDF assets](https://github.com/elma-123/portfolio/tree/main/assets): static documents · Publications, certificates, and project papers · `assets`

### External

Third-party service integration

- **EmailJS**: third-party service · Client-side contact form delivery

### Other components

- **Browser**: runtime · Client-side execution boundary

## Connections

- Browser → Home page: loads · Browser renders the portfolio page
- Browser → Compiled CSS: applies · Browser uses compiled styling
- Browser → Interactions: executes · Browser runs client interactions
- Browser → PDF assets: serves · Linked PDFs are downloaded or opened from static hosting
- Home page → Compiled CSS: links · Page consumes the generated stylesheet
- Home page → Interactions: boots · Page loads the interaction script
- Home page → PDF assets: references · Portfolio content links to static documents
- Custom styles → Compiled CSS: builds into · Custom CSS is incorporated into the compiled bundle
- Tailwind config → Compiled CSS: configures · Tailwind settings shape the generated CSS
- PostCSS config → Compiled CSS: processes · PostCSS participates in stylesheet generation
- Interactions → EmailJS: submits form · Contact form sends messages through EmailJS
