How smitronix/personal-project works
This repository is a collection of mostly independent personal projects rather than one integrated application. The main architectural boundary is the folder level: each subdirectory is its own self-contained app, demo, or lab, with no clear shared runtime or cross-project code reuse.
1. Repository-level structure
The repo contains several standalone front-end apps, one React/Vite desktop-shell app, one PHP form system, one Node-based JSON manager, and one C lab artifact. For an architecture diagram, treat each top-level project as a separate system.
2. BWP-2: the most layered front-end project
BWP-2 is a multi-page static web project with HTML entry points, shared CSS, client-side JavaScript, image assets, and an XML/XSD/XSL trio. It appears to be the most architecturally rich repo in the set.
3. BWP-2 presentation flow
Pages such as index.html, auth.html, advanced-3d.html, hand-3d-live.html, and walkman-loop.html load shared and page-specific styles from css/ and behaviors from js/. This is a browser-only application boundary: rendering and interaction happen entirely client-side.
4. BWP-2 functional areas
The JS files are split by feature: auth.js for authentication UI, advanced-3d.js and hand-3d-live.js for 3D/animation experiences, and walkman-loop.js for another animation page. css/style.css plus specialized styles support those views. The project is organized by experience rather than by backend domain.
5. BWP-2 XML documentation/data layer
xml/dfds.xml, dfds.xsd, and dfds.xsl form a separate structured-document pipeline: XML content, schema validation, and XSL transformation. This suggests an internal documentation or diagram artifact flow distinct from the front-end pages.
6. Nexus OS: React desktop environment
nexus-os is a Vite-based React application that simulates a desktop OS UI. Its architecture is component-driven: App.jsx composes Desktop, Taskbar, StartMenu, Window, ContextMenu, Notifications, BootScreen, and DesktopIcon, with app modules under components/apps/.
7. Nexus OS state and UI orchestration
Shared application state lives in src/core/store.js, which likely coordinates windows, app launch, taskbar state, notifications, and desktop interactions. main.jsx bootstraps the React tree, and src/styles/index.css provides the global shell styling. This is a pure client-side SPA with no visible backend dependency.
8. Nexus OS embedded apps
The “Browser” and “Settings” components under components/apps/ are windowed apps hosted inside the desktop shell. The architecture boundary here is important: the OS shell manages windowing and global state, while each app is a child module rendered inside a generic window container.
9. Simple static front-end projects
e-commerce, user-registration-portal, and js-task-dashboard are lightweight browser apps built from HTML/CSS/JS. They follow the classic static pattern: single-page UI, client-side interaction, and no explicit server layer in the repo.
10. PHP registration system
php-registration-system is a small server-rendered or server-handled form app. index.php is the entry point, style.css handles presentation, and registrations.json is the persistence store. The key architectural flow is browser form submission into PHP, then file-based JSON storage.
11. Node JSON manager
json-manager-node is a Node.js utility/service centered on index.js and database.json. Its architecture is file-backed JSON manipulation rather than a database server, making the file system the persistence boundary.
12. Demo and lab artifacts
js-basics-demo and js-task-dashboard are instructional browser demos. C-Lab/if-else.c and if-else.exe are a compiled C exercise, separate from the web stack. These should be treated as isolated learning modules, not subsystems of the larger apps.
13. Cross-cutting pattern across the repo
Most projects are self-contained and use local assets plus client-side logic, with persistence only in a few cases (registrations.json, database.json, XML docs). The repository has no shared service layer, API gateway, or common library layer tying the projects together.
14. Diagramming implication
If you draw an architecture diagram, model the repo as a portfolio of independent systems grouped by technology: static browser apps, a React desktop shell, a PHP file-backed form system, a Node JSON utility, and a C lab artifact. The strongest internal subsystem detail exists in BWP-2 and nexus-os.
Main entry points: BWP-2 BWP-2 · nexus-os nexus-os · e-commerce/index.html Static apps · BWP-2/index.html Pages
Components 19
Static browser apps
Independent client-side web projects with HTML/CSS/JS.
- Static apps · Lightweight standalone HTML/CSS/JS projects such as e-commerce, registration portal, and task dashboard.
e-commerce/index.html - e-commerce · Simple browser front-end with local scripting and styling.
e-commerce/index.html - Reg portal · Client-side registration portal with HTML, script, and style assets.
user-registration-portal/index.html - Task dashboard · Instructional browser dashboard built from local HTML/CSS/JS.
js-task-dashboard/index.html
BWP-2
Most layered static web project with page, asset, and XML document flows.
- BWP-2 · Multi-page browser-only experience with shared styles, page scripts, assets, and an XML/XSD/XSL documentation pipeline.
BWP-2 - Pages · Main and feature pages such as index, auth, and 3D/animation views.
BWP-2/index.html - Styles · Shared and page-specific presentation rules for the BWP-2 experiences.
BWP-2/css/style.css - Scripts · Feature-oriented browser logic for auth, 3D, and animation pages.
BWP-2/js/auth.js - Assets · Local image assets consumed by the BWP-2 pages.
BWP-2/assets/images - XML flow · Structured-document pipeline for XML content, schema validation, and transformation.
BWP-2/xml/dfds.xml
nexus-os
React desktop-shell application with windowed child apps and shared UI state.
- nexus-os · Vite-based React desktop environment with window management, taskbar, notifications, and embedded apps.
nexus-os - Boot · Initial boot/loading experience for the desktop shell.
nexus-os/src/components/BootScreen.jsx - Desktop UI · Core desktop surface and chrome: desktop, taskbar, start menu, window, context menu, notifications, and icons.
nexus-os/src/components/Desktop.jsx - Store · Shared client-side state coordinating windows, app launch, and desktop interactions.
nexus-os/src/core/store.js - Apps · Embedded desktop apps hosted inside the generic window container.
nexus-os/src/components/apps/Browser.jsx
Backend utilities
File-backed or server-handled projects outside the browser-only apps.
- PHP system · Server-handled registration flow persisting submissions to a JSON file.
php-registration-system/index.php - JSON manager · Node.js file-backed JSON tool centered on database.json and index.js.
json-manager-node/index.js
Lab artifacts
Standalone compiled or instructional exercises.
- C lab · Standalone compiled C practice artifact and source file.
C-Lab/if-else.c
Other components
- personal-project · A collection of mostly independent personal projects with no shared runtime or common application layer.
Connections 25
- personal-project → BWP-2: contains · Top-level project folder
- personal-project → nexus-os: contains · Top-level project folder
- personal-project → Static apps: contains · Top-level project folders
- personal-project → PHP system: contains · Top-level project folder
- personal-project → JSON manager: contains · Top-level project folder
- personal-project → C lab: contains · Top-level project folder
- BWP-2 → Pages: serves · HTML entry points drive the browser experiences
- BWP-2 → Styles: styles with · Shared and page-specific CSS
- BWP-2 → Scripts: behaves with · Client-side interaction logic
- BWP-2 → Assets: uses · Local image assets
- BWP-2 → XML flow: documents · Separate XML schema/transformation pipeline
- Pages → Styles: loads · Pages pull in CSS
- Pages → Scripts: loads · Pages pull in JS
- Pages → Assets: references · Pages embed local images
- XML flow → Styles: transforms with · XSL is part of the document workflow
- nexus-os → Boot: starts with · Boot/loading phase before the desktop shell
- nexus-os → Desktop UI: renders · Main shell and chrome
- nexus-os → Store: coordinates via · Shared UI state and window lifecycle
- nexus-os → Apps: hosts · Embedded apps inside the desktop container
- Desktop UI → Store: reads/writes · Desktop interactions and global state
- Desktop UI → Apps: opens · Windows render child apps
- Static apps → e-commerce: includes · Standalone browser app
- Static apps → Reg portal: includes · Standalone browser app
- Static apps → Task dashboard: includes · Standalone browser app
- PHP system → JSON manager: uses file storage pattern · Both persist state in local JSON files, but remain independent