How sertanozcnn/eo-creativeapp works
Project type and purpose
• From the file tree and README, we see a React single-page application (SPA) bootstrapped with Vite.
• It is a static front-end that uses Redux (RTK Query) to fetch content from remote APIs/CMS endpoints and organizes its UI into reusable components and pages.
File structure
• Top-level config and metadata:
• .env, package.json / package-lock.json, vite.config.js, tailwind.config.js, eslint.config.js
• Public/static assets:
• public/, src/assets/ (fonts, images)
• Application source code under src/:
• src/main.jsx + index.html – entry points
• src/router/router.jsx – SPA routing layer (likely React Router)
• src/redux/ – state management:
– features/ (slice definitions)
– services/ (RTK Query endpoints per content type)
– store/store.js (configureStore)
• src/components/ – atomic and composite UI components (AboutWes, Brands, Header, Footer, etc.)
• src/pages/ – route-level page components (Home, About, Contact, Pricing, Policy, Error404, etc.)
• src/App.jsx + App.css – root application shell
README for additional insights
• The README confirms React + Vite tooling, plus HMR and ESLint setup.
• No explicit backend is delivered in this repo; all dynamic data comes from external HTTP APIs (configured in Redux services).
a. Main components
• Browser / Client (React SPA)
• Static asset server or CDN (serves index.html, JS/CSS bundles, images/fonts)
• Routing layer (React Router in router.jsx)
• UI component hierarchy (App → Pages → Composite Components → Atoms)
• State management layer (Redux store + RTK Query services)
• External APIs / CMS endpoints (REST or GraphQL services hosting content)
b. Relationships and interactions
• User → Browser (UI interactions and route changes)
• Browser (React Router) serves the correct Page component
• Page components dispatch Redux actions or RTK Query hooks to fetch data
• RTK Query services make HTTP calls to external API endpoints
• Responses flow back to the Redux store, triggering re-renders of connected components
• Static assets (images, fonts) are requested from the public folder or CDN
c. Architectural patterns and design principles
• SPA pattern with client-side routing
• Component-based UI (atomic design within src/components)
• Unidirectional data flow via Redux
• RTK Query for data fetching and cache management
• Code separation: router, store, services, components, pages
d. Key technologies
• React + JSX for UI
• Vite as development/build tool
• Tailwind CSS for styling (tailwind.config.js)
• Redux Toolkit with RTK Query for state & data fetching
• ESLint for linting, PostCSS for CSS processing