# remirobichet/reco-cultu-floodcast architecture

> Architecture diagram of the GitHub repository remirobichet/reco-cultu-floodcast, 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/remirobichet/reco-cultu-floodcast
- Repository: https://github.com/remirobichet/reco-cultu-floodcast

## Overview

##### Main Components
a. Client/Browser Layer – Representing the end users’ web browsers.
b. Nuxt 3 Application – This is the core framework wrapping the entire frontend logic.
- Pages: Under the "pages" directory, each page (e.g., index.vue, participant pages, dynamic [id] pages) represents a distinct route.
- Layouts: Found in the "layouts" directory (e.g., default.vue) which define the common structure for the pages.
- Components: The rich, granular UI components located in the "components" directory. This folder is subdivided into atoms (several basic UI parts like Avatar, Badge, Button, Card, Dialog, Dropdown, Input, Sheet, Tooltip) that are reused across different parts of the application.
- Assets: For styling (like Tailwind CSS in assets/css/tailwind.css) and any static resources.
- _data: Contains local JSON files (participant_S9.json, podcast_S9.json, index.ts) that likely simulate or act as a data source during development.
c. Plugins & External Services:
- Plugins: In particular, the "plugins/00.supabase.ts" indicates integration with Supabase, so include an external service node named “Supabase” and show its connection to the Nuxt application.
d. Utility Libraries:
- lib: Contains utility functions that support various functionalities across the app.
e. Server-Side Elements:
- The "server" directory that contains server configuration (tsconfig.json) and might be used for server routes/APIs.
f. Configuration and Build:

##### Relationships and Interactions
- The User (client/browser) interacts with the Nuxt application by requesting pages.
- The Pages (Vue templates) orchestrate the layout and dynamically load Components.
- Components (UI elements) are styled using assets (Tailwind CSS) and are assembled on pages to form interactive interfaces.
- The _data folder supplies static/mock data to drive parts of the UI (e.g., participant and podcast details).
- The Plugins layer (e.g., Supabase plugin) manages external integrations and data fetching or authentication that the application uses during runtime.
- Utilities in the lib folder can be called by pages or components to handle common operations.
- Server routes (if used) may be called by pages/components to process backend logic.

##### Architectural Patterns and Design Principles
- This project follows a modular front-end architecture typical of modern Nuxt (or Vue) applications.
- It utilizes the “convention-over-configuration” concept from Nuxt: directories like pages, layouts, and components are auto-registered.
- There is a clear separation of concerns:
- Presentation: pages, layouts, and components.
- Styling: assets (including Tailwind CSS).
- Data logic and integrations: _data, plugins (like Supabase), and server files.
- Use of external configuration files (nuxt.config.ts, tsconfig.json, package.json) indicates adherence to good practices for maintainability and scalability.

## Diagram (Mermaid)

```mermaid
flowchart TD
    U["User Browser"]:::browser

    subgraph "Nuxt 3 Application"
        direction TB
        P["Pages"]:::core
        L["Layouts"]:::core
        C["Components"]:::core
        A1["Assets (Tailwind CSS)"]:::core
        D["_data (Local JSON Data)"]:::core
        Pl["Plugins (Supabase)"]:::external
        Li["Lib (Utility Libraries)"]:::core
        S["Server"]:::core

        P -->|"renders"| L
        P -->|"loads"| C
        C -->|"styled_by"| A1
        D -->|"supplies"| C
        P -->|"calls"| Pl
        C -->|"calls"| Pl
        Pl -->|"responds"| P
        P -->|"utilizes"| Li
        P -->|"calls"| S
    end

    U -->|"requests"| P

    subgraph "Configuration & Build"
        direction TB
        N["Nuxt Config"]:::config
        PK["Package JSON"]:::config
        TWC["Tailwind Config"]:::config
        TSC["Server TSConfig"]:::config
    end

    N ---|"configures"| P

    click P "https://github.com/remirobichet/reco-cultu-floodcast/tree/main//pages"
    click L "https://github.com/remirobichet/reco-cultu-floodcast/blob/main//layouts/default.vue"
    click C "https://github.com/remirobichet/reco-cultu-floodcast/tree/main//components"
    click A1 "https://github.com/remirobichet/reco-cultu-floodcast/blob/main//assets/css/tailwind.css"
    click D "https://github.com/remirobichet/reco-cultu-floodcast/tree/main//_data"
    click Pl "https://github.com/remirobichet/reco-cultu-floodcast/blob/main//plugins/00.supabase.ts"
    click Li "https://github.com/remirobichet/reco-cultu-floodcast/tree/main//lib"
    click S "https://github.com/remirobichet/reco-cultu-floodcast/tree/main//server"
    click N "https://github.com/remirobichet/reco-cultu-floodcast/blob/main/nuxt.config.ts"
    click PK "https://github.com/remirobichet/reco-cultu-floodcast/blob/main/package.json"
    click TWC "https://github.com/remirobichet/reco-cultu-floodcast/blob/main/tailwind.config.js"
    click TSC "https://github.com/remirobichet/reco-cultu-floodcast/blob/main//server/tsconfig.json"

    classDef browser fill:#AEDFF7,stroke:#333,stroke-width:2px;
    classDef core fill:#FFF2CC,stroke:#666,stroke-width:2px;
    classDef external fill:#DCEDC8,stroke:#333,stroke-width:2px;
    classDef config fill:#F8BBD0,stroke:#333,stroke-width:2px;
```
