How sofardy/wiut-frontend works
Project type and purpose
• This is a single-page application (SPA) built with React (bootstrapped via Create React App).
• Its folder structure, “src/components,” “src/pages,” “src/routers,” etc., plus asset folders for styles, images, fonts, indicates a client-side e-commerce or product-display application.
File structure
• Top-level directories:
• public – static index.html, manifest.json, robots.txt
• src – all application source code
• build – production output (HTML, CSS, JS bundles, assets)
• Within src:
• assets – fonts, images, global & abstract SCSS/CSS
• components – reusable UI pieces (headers, product cards, sidebars)
• layouts – wrappers for admin, client, or no-layout pages
• pages – entry-point components wired to routes
• routers – React Router setup and middleware
• hooks – custom React hooks
• Config/build scripts:
• package.json – dev and prod dependencies, scripts (start/test/build)
• webpack/babel hidden under CRA (ejected or abstracted).
Insights from the README
• Standard CRA commands: start, test, build, eject.
• Nothing custom beyond default – no server code here, purely front end.
Detailed but focused
• Build pipeline: npm scripts → CRA webpack → build/ folder → deployment target.
• Every significant architectural element to help new engineers understand the code structure, data flow, and deployment model at a glance.