How mohamedv0/angular-ecommerce works
Project type and purpose
• FreshCart is a full-stack e-commerce application, but the repository itself contains only the Angular frontend. It delivers a production-ready shopping experience—product catalog, cart, checkout, wishlist, user profile, theming, and i18n—all wired against a provided REST API (https://ecommerce.routemisr.com/api/v1).
• Key indicators: Angular 20 framework, PrimeNG UI library, Tailwind CSS styling, signal-based state management, ngx-translate for i18n, feature-based folder structure.
File structure
• Top-level:
• angular.json, tsconfig*.json, tailwind.config.js — build and tooling config
• public/i18n — runtime translation files
• src/app:
– core: constants, guards, interceptors, layout, models, services
– features: feature folders (auth, home, products, cart, checkout, wishlist, categories, brands, profile) each with routes.ts, services, models, components
– shared: reusable components, pipes, validators, utils
– theme: PrimeNG preset definitions
• src/environments — environment configs
• src/main.ts, app.ts, app.routes.ts — bootstrap and root routing
README for additional insights
• The README explicitly calls out:
• Feature-based architecture
• Lazy-loaded routes
• Signal-based state stores (@ngrx/signals)
• Comprehensive i18n (English & Arabic)
• Runtime theming with presets and dark/light mode
• External REST API as backend, no embedded server code
Final advice
• Don’t overcomplicate: capture modules, services, stores, data‐flow, and third-party integrations.