UI: switch to Syncfusion M3, remove Tailwind;

paginate changelog; docs updated; bump to 2025.1.0-alpha.8

README.md

@@ -132,7 +132,8 @@ For detailed deployment instructions, see:
 
 ### 🖥️ **Dashboard** (`dashboard/`)
 - **Technology**: React 19 + TypeScript + Vite
-- **UI Framework**: Syncfusion components + Tailwind CSS
+- **UI Framework**: Syncfusion components (Material 3 theme)
+- **Styling**: Centralized Syncfusion Material 3 CSS imports in `dashboard/src/main.tsx`
 - **Features**: Responsive design, real-time updates, file management
 - **Port**: 5173 (dev), served via Nginx (prod)
 
@@ -270,13 +271,15 @@ mosquitto_sub -h localhost -t "infoscreen/+/heartbeat" -v
 
 ## 🎨 Frontend Features
 
-### Syncfusion Components Used
+### Syncfusion Components Used (Material 3)
 - **Schedule**: Event calendar with drag-drop support
 - **Grid**: Data tables with filtering and sorting
 - **DropDownList**: Group and period selectors
 - **FileManager**: Media upload and organization
 - **Kanban**: Task management views
 - **Notifications**: Toast messages and alerts
+ - **Pager**: Used on Programinfo changelog for pagination
+ - **Cards (layouts)**: Programinfo sections styled with Syncfusion card classes
 
 ### Pages Overview
 - **Dashboard**: System overview and statistics
@@ -286,6 +289,7 @@ mosquitto_sub -h localhost -t "infoscreen/+/heartbeat" -v
 - **Media**: File upload and conversion
 - **Settings**: System configuration
 - **Holidays**: Academic calendar management
+ - **Program info**: Version, build info, tech stack and paginated changelog (reads `dashboard/public/program-info.json`)
 
 ## 🔒 Security & Authentication
 
@@ -415,3 +419,35 @@ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
 ---
 
 For detailed technical documentation, deployment guides, and API specifications, please refer to the additional documentation files in this repository.
+
+Notes:
+- Tailwind CSS was removed. Styling is managed via Syncfusion Material 3 theme imports in `dashboard/src/main.tsx`.
+
+## 🧭 Changelog Style Guide
+
+When adding entries to `dashboard/public/program-info.json` (displayed on the Program info page):
+
+- Structure per release
+   - `version` (e.g., `2025.1.0-alpha.8`)
+   - `date` in `YYYY-MM-DD` (ISO format)
+   - `changes`: array of short bullet strings
+
+- Categories (Keep a Changelog inspired)
+   - Prefer starting bullets with an implicit category or an emoji, e.g.:
+      - Added (🆕/✨), Changed (🔧/🛠️), Fixed (🐛/✅), Removed (🗑️), Security (🔒), Deprecated (⚠️)
+
+- Writing rules
+   - Keep bullets concise (ideally one line) and user-facing; avoid internal IDs or jargon
+   - Put the affected area first when helpful (e.g., “UI: …”, “API: …”, “Scheduler: …”)
+   - Highlight breaking changes with “BREAKING:”
+   - Prefer German wording consistently; dates are localized at runtime for display
+
+- Ordering and size
+   - Newest release first in the array
+   - Aim for ≤ 8–10 bullets per release; group or summarize if longer
+
+- JSON hygiene
+   - Valid JSON only (no trailing commas); escape quotes as needed
+   - One release object per version; do not modify historical entries unless to correct typos
+
+The Program info page paginates older entries (default page size 5). Keep highlights at the top of each release for scanability.