How blueedgetechno/win11react works
Project type and purpose
• This is a single‐page application (SPA) built in React+Redux that mimics the Windows 11 desktop experience in a browser or as a desktop app via Tauri.
• It’s a PWA (manifest, service worker) and also packaged into a native desktop application using Tauri (Rust backend).
File structure
• Top level:
• public/ – static assets (HTML, CSS, JS, images, PWA manifest, service worker)
• src/ – React application (components, containers, actions, reducers, utils)
• src-tauri/ – Rust/Tauri code for native desktop wrapper (main.rs, build.rs, configuration)
• Configuration files: package.json, vite.config.js, tailwind.config.js, .firebaserc, crowdin.yml (CI/CD, localization), GitHub Actions, Dockerfiles, Procfile for Heroku
Key architecture notes from README
• No backend API: purely front‐end logic, state managed with Redux
• Optional hosting on static servers (Netlify, Vercel, Docker, Heroku)
• Localization managed with Crowdin and i18next
• PWA features for offline support (serviceWorker.js)
• Desktop native features via Tauri
Main components and their interactions
a. Browser / Desktop Shell (Tauri)
• Hosts the React SPA in a WebView (Tauri’s window)
• Exposes native APIs (filesystem, settings) to JS via Tauri bridge
b. React + Redux SPA
• UI Components (src/components)
• Containers/Pages (src/containers)
• State Management (src/actions ↔ src/reducers)
• Styling: SCSS, CSS modules, Tailwind
c. Static Asset Server / CDN
• Serves public/index.html, JS bundles, CSS, images
• PWA manifest and service worker for caching
d. CI/CD & Localization
• GitHub Actions for build & deploy
• Crowdin for translation sync
e. Deployment environments (optional microservices)
• Docker container, Heroku, Netlify, Vercel, Firebase hosting