From 6010666dcfff21d39eff405e041795ca78f4cdfc Mon Sep 17 00:00:00 2001 From: ramforth Date: Mon, 17 Nov 2025 10:35:51 +0100 Subject: [PATCH] Fix: small type-o --- CONTEXT.md | 7 +++++++ README.md | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/CONTEXT.md b/CONTEXT.md index 45c3fe8..1f97ff5 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -48,6 +48,13 @@ The project is built on the "hybrid architecture" detailed in the `RESEARCH_REPO Based on the `TASKS.md` file, the only remaining task for Phase 1 is: * **Task 1.4: Basic Session Management:** After a user successfully logs in, we need to create a persistent session for them. This will allow us to "remember" who is logged in, protect routes like the future `/dashboard`, and provide a seamless user experience. The current flow correctly authenticates the user but does not yet establish this persistent session. +### Dashboard Progress (Phase 2) +We have started work on Phase 2, focusing on the user dashboard. The following features have been implemented on the `feature/dashboard-ui` branch: +* **Dynamic Dashboard:** The dashboard now uses the Jinja2 templating engine to dynamically display the logged-in user's username and their unique overlay URL. +* **Theme Selection:** A theme selection dropdown has been added to the dashboard, allowing users to choose between a "Dark Purple" and a "Bright Green" overlay theme. +* **Settings API:** A `/api/settings` endpoint has been created. This endpoint handles saving the user's chosen theme to the database. +* **Dynamic Overlay Theming:** The `/overlay/{user_id}` endpoint now dynamically loads the correct HTML template based on the user's saved theme preference, providing a personalized overlay. + ## References: ### Development plan diff --git a/README.md b/README.md index ac294a7..2f6eb24 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ This project is currently in **Phase 1: Initial Development**. User privacy and security are paramount. All sensitive user credentials, such as OAuth access and refresh tokens from external platforms, are **always encrypted** before being stored in the database. They are never stored in plain text, ensuring a high standard of security for user data. -## � Technology Stack +## 🖥️ Technology Stack * **Backend:** Python 3.9+ (FastAPI) * **Database:** SQLite (initially, for simplicity) with SQLAlchemy