How paradox-bssm/windeath44.server.frontend works
Project Type and Purpose
• This is a single-page, front-end web application built with React + TypeScript and Vite.
• It provides a dynamic UI (“applications” folder) with shared components, styling, state management, and low-level modules.
High-Level Architectural Components (excluding API)
a. Presentation Layer
• src/applications: Page-level React components (each “application” view).
• src/applications/components: Reusable UI components (buttons, inputs, menus, message blocks).
• src/applications/layout: Common layout components.
b. Styling
• src/Theme.css, src/assets/font.css, component-level style.ts files.
c. State Management & Reactivity
• src/atoms: Global state atoms (Recoil/Zustand style).
• src/hooks: Custom React hooks for state updates and side-effects.
d. Core Modules & Utilities
• src/lib: Helper functions (cursor setup, custom tag parsing).
• src/modules: Core TypeScript interfaces, enums, type definitions.
e. Application Services
• src/services: Client-side “kernel” boot logic, window management, task definitions.
f. Configuration & Build
• vite.config.ts, tsconfig.json / tsconfig.path.json, ESLint, Prettier configs, .gitignore.
Relationships and Interactions
• Browser loads public/index.html → bootloader (src/bootLoder.tsx) → service kernel (src/services/kernel.tsx).
• Service kernel initializes window manager → renders root React tree under src/applications/seori.tsx.
• Presentation Layer components consume state from atoms via hooks and dispatch actions to services.
• Hooks and services invoke core modules (src/modules) and utility functions (src/lib).
• Assets and CSS feed into components for styling and layout.
Important Patterns and Principles
• Component/Container separation: page-level views in applications vs. UI building blocks in applications/components.
• Atomic state via atoms + React hooks for subscription.
• Service-oriented initialization: kernel boot → window/task management.
• TypeScript interfaces enforce strict typing across modules, services, and components.
4. Around Root App, group applications/ and applications/components/ as the Presentation Layer.
6. To the side, place services/, connect State Management to Services for side-effects.