# isaias-dr/creador-de-horarios architecture

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

- Interactive diagram: https://gitdiagram.com/isaias-dr/creador-de-horarios
- Repository: https://github.com/isaias-dr/creador-de-horarios

## Overview

##### Main Components
- User Interface (UI) Layer:
- index.html: The entry point that renders and orchestrates the interface.
- css folder: Contains styles which define the visual look and feel.
- js folder (with no.js): Implements the client-side logic including schedule creation and data processing.

- Data Assets Layer:
- asset folder: Stores CSV and JSON files (for multiple semesters and formats) that contain schedules or course-related data. This folder holds preprocessed data originally from the Duoc UC’s published Excel files.

- External Data Source (Contextual Component):

##### Relationships and Data Flow
- From index.html, the browser pulls in CSS and JavaScript resources.
- The JavaScript file (no.js) acts as the schedule builder engine by:
- Loading and processing the data from the asset directory (CSV/JSON files).
- Parsing the data into usable formats.
- Rendering schedule options and assisting students in building desired timetables.
- Optionally, include a connection (or annotation) showing how external data from Duoc UC (the originally published Excel files) eventually is converted and stored into the asset folder.

##### Architectural Patterns and Principles
- Separation of Concerns: Clearly separate static presentation (HTML/CSS) from business logic (JavaScript) and from raw data storage (asset folder).
- Client-Side Processing: The architecture primarily executes in the user’s browser, emphasizing a static site design without a backend server.
- Data Input Pipeline: Demonstrate that schedule data is ingested from external sources, preprocessed into CSV/JSON formats, and then consumed by the client application.

##### Inclusion of Relevant Technologies/Libraries
- The project is built with standard web technology (HTML, CSS, JavaScript).
- Any JavaScript libraries or frameworks (if used later or implied) should be documented as part of the business logic layer.
- The design could also mention browser-based APIs (for file fetching/parsing) if applicable.

## Diagram (Mermaid)

```mermaid
flowchart TD
    A("User Browser"):::external
    subgraph "Browser UI"
        HTML("index.html"):::ui
        CSS("css folder"):::ui
        JS("js folder (no.js)"):::logic
        IMG("img folder"):::ui
    end
    D("Data Assets Repository"):::data
    E("Duoc UC External Data Service"):::externalService

    A -->|"Loads"| HTML
    HTML -->|"Loads"| CSS
    HTML -->|"Loads"| JS
    HTML -->|"Loads"| IMG
    JS -->|"ParsesData"| D
    E -->|"ProvidesExcelData"| D

    click HTML "https://github.com/isaias-dr/creador-de-horarios/blob/main/index.html"
    click CSS "https://github.com/isaias-dr/creador-de-horarios/tree/main/css"
    click JS "https://github.com/isaias-dr/creador-de-horarios/blob/main/js/no.js"
    click IMG "https://github.com/isaias-dr/creador-de-horarios/tree/main/img"
    click D "https://github.com/isaias-dr/creador-de-horarios/tree/main/asset/"

    classDef ui fill:#f9f,stroke:#333,stroke-width:2px;
    classDef logic fill:#bbf,stroke:#333,stroke-width:2px;
    classDef data fill:#afa,stroke:#333,stroke-width:2px;
    classDef external fill:#ffa,stroke:#333,stroke-width:2px;
    classDef externalService fill:#ff9,stroke:#333,stroke-width:2px;
```
