How shivamkumar24/myntra_clone works
Project Type and Purpose
• This is a front-end e-commerce website clone built using HTML, CSS, and advanced JavaScript (with ES6 features).
• Its purpose is to mimic Myntra’s fashion and lifestyle e-commerce portal, complete with user registration (signin/signup), multiple product category pages (Men, Women, Kids, Home & Living, Beauty), and shopping cart functionality.
• There is no separate backend layer visible here – data persistence and user/session management (e.g., using Local Storage) are handled client-side.
File Structure
• Top-Level Components:
• Standalone pages such as index.html, Home.js, home.html, and beauty.* files.
• Specific feature directories: “Register” for managing signin and signup flows, “cartPage” for the shopping cart, checkout, address handling, and order success pages.
• Category-specific directories: “menPage”, “womenPage”, “kidsPage” – each containing listings and product details.
• “components” directory: Contains shared modules like navbar.js, footer.js, and associated CSS files. These are reusable UI fragments utilized across multiple pages.
• The separation of files into distinct directories suggests a modular and component-based approach, which helps in isolating the user interface into manageable pieces. This also indicates a “page/component” based architecture where similar functionalities (e.g., registration or product categories) are knitted together using shared common elements.
README Insights
• The README highlights that the project is a clone of Myntra, stressing the importance of a user-friendly, navigable interface.
• It outlines the teams involved and even provides live Netlify and GitHub links for deployment and source control, reinforcing that this is a client-side heavy project with a focus on UI, navigation, and local client storage.
• The skills mentioned (HTML, CSS, Advanced JS, Local Storage, ES6) confirm that no server-side architecture is meant to be diagrammed here.
a. Main Components to Represent:
• User Interface (UI) Layer: Displaying pages such as Home, Product Categories (Men, Women, Kids, etc.), Beauty, Home-Living, etc.
• Navigation Components: The shared “navbar” and “footer” that appear across pages.
• Registration/Authentication: Grouped under the “Register” folder (signin and signup screens and associated scripts/styles).
• Cart & Checkout Flow: Divided into several sub-components – Cart display, address entry, checkout, OTP, and order success.
• Category Pages: Each category has its own folder (menPage, womenPage, kidsPage, etc.) indicating category-specific product listings and details.
• Data/State Management: Although not a “service” in the backend sense, highlight the use of Local Storage for persisting session data, cart items, and user credentials.
b. Relationships and Interactions:
• The Navigation components (navbar/footer) are injected into every page.
• The Home page (index.html/home.html) acts as the entry point, linking to various category pages.
• Registration components allow users to sign in/up, which then influences access to cart functionalities.
• The Cart system interacts with Local Storage to keep track of product selections, flowing from cart display to checkout to order confirmation.
• While each category page is a standalone UI module, they maintain a consistent look and feel by reusing common components.
c. Architectural Patterns/Design Principles:
• Component-based UI: Reusable “navbar” and “footer” components.
• Modular page structure: Pages are organized into functional folders to isolate their logic and style.
• Client-side state management: Use of local storage for handling state without server interaction.
• Clear separation of concerns: Distinct directories for registration, cart management, and product categories.
d. Relevant Technologies:
• HTML and CSS for structure and presentation.
• Advanced JavaScript (ES6) for interactivity and state management.
• Local Storage for persisting data between user sessions.