refactor: drop toast + over-engineered extras, add inline admin feedback

Phase 1 cleanup of the personal-site revamp. Backend/architecture untouched; changes are limited to removing unused complexity and restoring feedback. Removals - Toast system: delete react-hot-toast, Toaster, QueryToastBridge, lib/toast, the toggle/easter-egg calls, related i18n keys and the dependency. - Contact protection: remove Turnstile + per-IP rate limiting (lib/contact-guard, lib/contact-protection, admin screen, form widget, app-config wiring, nav entry, test). - Speculative specs: delete orders, products, downloads, project-inquiry. Inline feedback (replaces toast, no new deps) - Add lib/admin-feedback (withFlash/readFlash) and components/admin/admin-flash, rendered centrally by AdminDashboardShell. - Emit success/error messages for media, site-settings, portfolio, smtp, marquee and maintenance actions; pages read them via searchParams. - Contact form shows validation/delivery errors inline; success still redirects to /success. Docs - Fix stale paths in frontend-system-* (components/root -> components/admin, lib/root-navigation -> lib/admin-navigation, drop phantom src/) and remove contact-protection references from docs and CLAUDE.md. - Add docs/PHASE0_DIAGNOSIS.md (diagnosis report). Note: proxy.ts self-fetch kept intentionally; it also drives maintenance mode.
2026-07-14 21:03:51 +02:00
parent 1a7b3397f6
commit d48497b992
62 changed files with 443 additions and 1453 deletions
@@ -1,39 +0,0 @@
-# Downloads Feature Spec
-
-## Current Implementation
-
- Portfolio assets support
-
-`DOCUMENT`
-
-files
- Portfolio detail pages expose document links with an
-
-`Open document`
-
-action
- Media library can store document assets
-
-## Gaps
-
- No standalone downloads index exists
- No download access rules exist
- No download analytics or gating exists
- No dedicated
-
-`Download`
-
-model exists
-
-## Proposed Scope
-
-This is a proposed feature, not an implemented one.
-
- Central downloads listing
- Optional download categories
- Optional gated download access
- Download tracking
-
-## Recommended First Step
-
- Decide whether downloads remain a portfolio asset type or become their own domain
@@ -1,29 +0,0 @@
-# Orders Feature Spec
-
-## Current Implementation
-
- No
-
-`Order`
-
-model exists
- No checkout flow exists
- No payment integration exists
- No admin order management exists
-
-## Proposed Scope
-
-This is a proposed feature, not an implemented one.
-
- Order creation from products or inquiry conversions
- Order status lifecycle
- Admin order review and fulfillment tracking
- Email notifications for order events
-
-## Recommended First Step
-
- Clarify whether
-
-`orders`
-
-means ecommerce checkout, service bookings, or manual sales records
@@ -1,40 +0,0 @@
-# Products Feature Spec
-
-## Current Implementation
-
- No
-
-`Product`
-
-model exists
- No public
-
-`/products`
-
-route exists
- No admin CRUD exists for products
- The site header contains a disabled
-
-`Products`
-
-navigation item marked as
-
-`Soon`
-
-## Proposed Scope
-
-This is a proposed feature, not an implemented one.
-
- Public product listing page
- Product detail page
- Product media and downloadable assets
- Admin product CRUD
- Optional relation from products to portfolio case studies
-
-## Recommended First Step
-
- Define a dedicated
-
-`Product`
-
-data model before any UI work
@@ -1,32 +0,0 @@
-# Project Inquiry Feature Spec
-
-## Current Implementation
-
- No separate
-
-`ProjectInquiry`
-
-model exists
- No dedicated project inquiry route exists
- Current CTAs route users to the generic contact form
-
-## Proposed Scope
-
-This is a proposed feature, not an implemented one.
-
- Inquiry form specifically for new project leads
- Optional prefilled source context from portfolio or homepage CTA
- Inquiry status tracking in admin
- Possible conversion into
-
-`Order`
-
-or CRM lead later
-
-## Recommended First Step
-
- Decide whether project inquiry should stay a specialized
-
-`contact`
-
-variant or become a persisted lead-management feature