How brokernlamp/testing1 works
Project Type and Purpose
• This is a monorepo containing two main subsystems:
a. A Windows desktop administration application (“SKS Admin Desktop”) built with .NET 8, WPF, Entity Framework Core, SQLite, following the MVVM pattern.
b. A customer-facing Next.js web application (TypeScript, React, Tailwind) with serverless API routes for e-commerce functions (cart, enquiries, uploads), backed by Supabase, ImageKit, and email services.
File Structure Analysis
• Top-level directories:
• Models/, Services/, App.xaml(.cs), MainWindow.xaml(.cs), appsettings.json → WPF app source
• SKS-Admin-Desktop/… → Visual Studio solution, build artifacts, bin/obj folders
• app/, components/, lib/, public/, etc. → Next.js frontend and API routes
• vagabonds-travel-blog-template-kit/… → static template kit (assets, JSON templates)
• Configuration files: appsettings.json (desktop), next.config.js, netlify.toml, env.example, tsconfig.json (web).
• Build scripts & manifests: .next/, package.json, nuget caches.
README Insights
• Desktop app features: dashboard, product/order/customer/inventory management, local SQLite DB, DI, MVVM.
• Technology stack for desktop: .NET 8, WPF, EF Core, SQLite.
a. Main Components
1. Desktop Subsystem
• UI Layer: WPF Views (XAML)
• ViewModels: MVVM binding layer
• Services Layer: business logic, AppDbContext (EF Core)
• Data Storage: local SQLite database (SKSAdmin.db)
2. Web Subsystem
• Frontend: Next.js pages under app/ + shared UI components
• API Layer: serverless routes (app/api/…/route.ts)
• Business Logic & Utilities: lib/auth.ts, lib/supabase.ts, lib/imagekit.ts, utils
• Data Storage: Supabase (PostgreSQL)
• External Services: ImageKit (media storage), Email SMTP provider
b. Relationships and Interactions
• Desktop UI → ViewModel → Services → EF Core → SQLite
• Web UI ↔ Next.js Server (SSR/CSR)
• Web UI → fetch()/Axios → API routes
• API routes → Supabase client for CRUD
• API routes → ImageKit SDK for file uploads
• API routes → Email service for quotations
c. Architectural Patterns & Principles
• Desktop: MVVM pattern, Dependency Injection for services, layered architecture (UI / VM / Services / Data)
• Web: Full-stack Next.js (React + serverless functions), modular UI components, API-as-backend
• Reuse of environment configs (.env), code-splitting via Next.js app directory
d. Key Technologies & Frameworks
• Desktop: .NET 8, WPF, Entity Framework Core, SQLite, MVVM, Microsoft DI
• Web: Next.js 14+, React, TypeScript, Tailwind CSS, Netlify deploy, Supabase SDK, ImageKit SDK