# leosilvagomes/repositorio-de-bordo architecture

> Architecture diagram of the GitHub repository leosilvagomes/repositorio-de-bordo, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-17). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/leosilvagomes/repositorio-de-bordo
- Repository: https://github.com/leosilvagomes/repositorio-de-bordo

## Overview

##### Main Components
- Content Sources & Data Storage:
– Directories such as _posts (blog entries), _about, _habilities, _profissional-experience, _project-experience, _qualification, and _volunteer-experience store Markdown files that represent personal writing, resume entries, project details, and qualifications.
– The user_info.yaml file holds personalized metadata/configuration.
- Presentation & Styling:
– _layouts, _includes, and _sections directories form the core of the templating system, rendering the content.
– css and _sass directories provide styling and responsive design.
- Build & Static Site Generation:
– The static site generator (Jekyll) takes the content, templates, and assets to generate the final website.
– The _config.yaml holds configuration info for the build.
- Automation & Scripting:
– Under the scripts directory, there are shell scripts for creating, deleting, and updating content (posts, experiences, skills, qualifications, and summary).
– The scripts/process_user_info.py and update_user_info.sh help automate updates to personalized data.
- CI/CD and Deployment:
– The .github/workflows directory contains YAML files that define automation for actions like editing files, deleting files, and deploying the site (via github-pages.yml).
- Repository & Versioning:
– Git files (like .gitignore) and the project’s overall file structure support version control and integration with GitHub, including issues templates.

##### Relationships and Interactions
- Archive/Content Management → Static Site Generator:
– Markdown files in various content directories feed into the Jekyll system.
– The layouts, includes, and sections are used by Jekyll to assemble and render pages.
- Build Process:
– GitHub actions (from the CI/CD pipeline) watch repository changes and trigger builds.
– The generated static site is then deployed, for example, via GitHub Pages.
- Custom Automation Scripts:
– Shell scripts in the scripts folder act as helper tools for content management (creation, deletion, update) and likely modify content or configuration files.
- User Interaction:
– Though this is a personal blog/portfolio, visitor interactions will be with the static pages that are generated. The architecture separation clearly distinguishes authoring (repository management) and consumption (deployed website).

##### Architectural Patterns and Design Principles
- Separation of Concerns:
– The project is clearly partitioned into content (Markdown files and YAML), presentation (HTML layouts, includes, and CSS/SASS styling), and automation (scripts and CI/CD workflows).
- Static Site Generation:
– Utilizing a static site generator ensures content is pre-rendered for fast and secure delivery without a dedicated backend server.
- Modular Structure:
– The organization into directories (e.g., separate folders for professional, project, and volunteer experiences) allows for modularity and ease of future scalability or replacement of components.
- Continuous Integration/Continuous Deployment (CI/CD):
– GitHub workflows capture the build/deploy processes, ensuring reliable updates on changes.

##### Elements
- Clear Labels:
- Visual Distinction:
- Detailed Breakdown:

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Content Repository Subgraph
    subgraph "Content Repository"
        CP1("Blog Posts"):::content
        CP2("About Info"):::content
        CP3("Habilities"):::content
        CP4("Professional Experience"):::content
        CP5("Project Experience"):::content
        CP6("Qualifications"):::content
        CP7("Volunteer Experience"):::content
        CP8("User Config"):::content
    end

    %% Presentation & Styling Subgraph
    subgraph "Presentation & Styling"
        PS1("Layouts"):::presentation
        PS2("Includes"):::presentation
        PS3("Sections"):::presentation
        PS4("CSS"):::presentation
        PS5("SASS"):::presentation
    end

    %% Build & Static Site Generation Subgraph
    subgraph "Build & Static Site Generation"
        B1("Jekyll Build Engine"):::build
        B2("Site Config"):::build
        B3("Gem Dependencies"):::build
    end

    %% Automation & Scripting Subgraph
    subgraph "Automation & Scripting"
        A1("Create Scripts"):::automation
        A2("Delete Scripts"):::automation
        A3("Process User Info (Python)"):::automation
        A4("Update User Info (Shell)"):::automation
    end

    %% CI/CD & Deployment Subgraph
    subgraph "CI/CD & Deployment"
        C1("GitHub Workflows"):::cicd
        C2("Deployment (GitHub Pages)"):::cicd
    end

    %% Relationships
    %% Content and Presentation feed into Build Engine
    CP1 -->|"feeds"| B1
    PS1 -->|"provides_templates"| B1
    CP8 -->|"config_updates"| B2

    %% Automation scripts interacting with content
    A1 -->|"creates_content"| CP1
    A2 -->|"deletes_content"| CP1
    A3 -->|"updates_config"| CP8
    A4 -->|"updates_config"| CP8

    %% CI/CD triggers build and deployment flows
    C1 -->|"triggers_build"| B1
    B1 -->|"deploys_site"| C2

    %% Additional connections from Build sub-components (for clarity)
    B2 --> B1
    B3 --> B1

    %% Class Definitions for Styling
    classDef content fill:#FFDEAD,stroke:#8B4513,stroke-width:2px;
    classDef presentation fill:#E6E6FA,stroke:#5D3FD3,stroke-width:2px;
    classDef build fill:#98FB98,stroke:#228B22,stroke-width:2px;
    classDef automation fill:#FFD700,stroke:#B8860B,stroke-width:2px;
    classDef cicd fill:#ADD8E6,stroke:#4682B4,stroke-width:2px;

    %% Click Events for Content Sources & Data Storage
    click CP1 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_posts"
    click CP2 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_about"
    click CP3 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_habilities"
    click CP4 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_profissional-experience"
    click CP5 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_project-experience"
    click CP6 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_qualification"
    click CP7 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_volunteer-experience"
    click CP8 "https://github.com/leosilvagomes/repositorio-de-bordo/blob/main/user_info.yaml"

    %% Click Events for Presentation & Styling
    click PS1 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_layouts"
    click PS2 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_includes"
    click PS3 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_sections"
    click PS4 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/css"
    click PS5 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/_sass"

    %% Click Events for Build & Static Site Generation
    click B2 "https://github.com/leosilvagomes/repositorio-de-bordo/blob/main/_config.yaml"
    click B3 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/Gemfile"

    %% Click Events for Automation & Scripting
    click A1 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/scripts/create/"
    click A2 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/scripts/delete/"
    click A3 "https://github.com/leosilvagomes/repositorio-de-bordo/blob/main/scripts/process_user_info.py"
    click A4 "https://github.com/leosilvagomes/repositorio-de-bordo/blob/main/scripts/update_user_info.sh"

    %% Click Events for CI/CD & Deployment
    click C1 "https://github.com/leosilvagomes/repositorio-de-bordo/tree/main/.github/workflows"
```
