# rmit-fintech-club/fintech-website architecture

> Architecture diagram of the GitHub repository rmit-fintech-club/fintech-website, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/rmit-fintech-club/fintech-website
- Repository: https://github.com/rmit-fintech-club/fintech-website

## Overview

##### Main Components
- Web Frontend (Next.js): Represent the overall Next.js application that includes:
- Layout & Providers: Include the layout.tsx and providers.tsx (likely used for app-wide theming and context providers, e.g., Jotai, next-themes, or Framer Motion for animations).
- Reusable UI Components: Include the components directory that houses elements like button.tsx, link.tsx, and navbar.tsx.
- Configuration & Styling:
- Config Directory: Illustrate configuration files for fonts, site settings, and themes (e.g., config/fonts.ts, config/site.ts, config/theme.ts).
- Styling & Assets: Show the styles directory (globals.css) and public assets.
- Third-Party Services / Libraries: Note the external technologies integrated – NextUI, Tailwind CSS (with tailwind.config.ts and postcss.config.js), Framer Motion, next-themes, Zod for validation, and support for MongoDB.

##### Relationships and Interactions
- The web frontend (pages) interacts with UI components to render various FinTech-related views (about, events, join-us, projects).
- The layout and providers are used to wrap the application, ensuring that UI themes, fonts, and state management are applied across all pages.
- Configuration elements dictate styling and behavior (e.g., using Tailwind for styling, next/font for font optimization) which should be linked to the application’s theming and global styling components.

##### Architectural Patterns
- File System-based Routing: Since Next.js uses the app directory as its route definitions, emphasize that each folder (and dynamic folder like [pid]) corresponds to a specific route in the application.
- Component-Based Architecture: Distinguish between page components (in app/) and reusable styled, functional components (in components/).
- Separation of Concerns: Show how configuration, styling, UI, and data management are clearly separated.
- Modern State and Theme Management: Include brief notes on libraries like Jotai and next-themes that manage the state and theme across the application.

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Frontend Layer"
        A["Pages (app/)"]:::frontend
        B["Layout (app/layout.tsx)"]:::frontend
        C["Providers (app/providers.tsx)"]:::frontend
        D["Reusable UI Components (components/)"]:::frontend
        E["Third-Party Libraries (NextUI,FramerMotion,next-themes,Zod)"]:::frontend
    end

    subgraph "Backend/Data Layer"
        F["Server-side API/Processing"]:::backend
        G["MongoDB"]:::database
    end

    subgraph "Configuration & Styling"
        H["Configuration (config/)"]:::config
        I["tailwind.config.ts"]:::config
        J["postcss.config.js"]:::config
        K["Global Styles (styles/globals.css)"]:::config
        P["Public Assets (public/)"]:::config
    end

    subgraph "CI/CD Pipeline"
        R[".github/workflows/"]:::ci
        S["biome.json"]:::ci
    end

    N["Client Browser"]:::client

    %% Flow connections
    N -->|"requests"| A
    A -->|"wrapped_by"| B
    A -->|"wrapped_by"| C
    A -->|"renders"| D
    E -->|"integrates_with"| D
    A -->|"API_call"| F
    F -->|"data_persistence"| G

    H -->|"configures"| A
    I -->|"sets_up"| K
    J -->|"sets_up"| K
    K -->|"applies_styles"| A
    P -->|"applies_assets"| A

    R -->|"deploys"| A
    S -->|"CI_config"| R

    %% Class definitions for colors and styles
    classDef frontend fill:#D6EAF8,stroke:#1B4F72,stroke-width:2px;
    classDef backend fill:#FCF3CF,stroke:#B7950B,stroke-width:2px;
    classDef database fill:#E8DAEF,stroke:#8E44AD,stroke-width:2px;
    classDef config fill:#D5F5E3,stroke:#1E8449,stroke-width:2px;
    classDef ci fill:#FADBD8,stroke:#C0392B,stroke-width:2px;
    classDef client fill:#FDEBD0,stroke:#D35400,stroke-width:2px;

    %% Click events for component mapping
    click A "https://github.com/rmit-fintech-club/fintech-website/tree/master/app/"
    click B "https://github.com/rmit-fintech-club/fintech-website/blob/master/app/layout.tsx"
    click C "https://github.com/rmit-fintech-club/fintech-website/blob/master/app/providers.tsx"
    click D "https://github.com/rmit-fintech-club/fintech-website/tree/master/components/"
    click H "https://github.com/rmit-fintech-club/fintech-website/tree/master/config/"
    click I "https://github.com/rmit-fintech-club/fintech-website/blob/master/tailwind.config.ts"
    click J "https://github.com/rmit-fintech-club/fintech-website/blob/master/postcss.config.js"
    click K "https://github.com/rmit-fintech-club/fintech-website/blob/master/styles/globals.css"
    click P "https://github.com/rmit-fintech-club/fintech-website/tree/master/public/"
    click R "https://github.com/rmit-fintech-club/fintech-website/tree/master/.github/workflows/"
    click S "https://github.com/rmit-fintech-club/fintech-website/blob/master/biome.json"
```
