System Architecture

Last updated: September 2026

System Architecture Overview

Click here to view HTML version ( here )

Shows the whole system flow: Browser → Router → Auth&RBAC → Controllers → Models → MariaDB (main path), branching out to Views/Themes (render) and System Services (backup/update, dashed line since it's admin-only, not every request).


Module/Data Map

Click here to view HTML version (here)

Shows User & RBAC as the center (aggregate root) → writes to Blog / Event / Page (each has an author_id linking back) and configures the "Platform & System" module, which groups Settings, FAQ, Hero Banner, License, and Activity Log into a single box (not split into sub-boxes, to avoid clutter).


Auth & Permission Flow

Click here to view HTML version (here)

This flowchart shows a single request passing through 3 checkpoints: session valid? → CSRF token valid? → has permission per RBAC? Only after clearing all three does it reach the Controller (highlighted in orange as the happy path). If a request fails any checkpoint, it branches off to its own response (302 redirect / 419 CSRF / 403 forbidden) — making it easy to see how many layers of defense the system has, which also works as a security selling point.