How waledroid/daq_numerique_2025 works
Site_Web_CodaQ – A static website that includes assets, custom CSS, and HTML.
3. hivegames-frontend – A more complex, single‑page application (SPA) built with modern JavaScript (using React, JSX components, Vite as a bundler, and likely npm dependencies) which includes a service layer (api.js) to handle external or backend interactions.
4. portfolio – A website meant for presenting your CV and projects, organized with its own assets and content pages.
And Isolate the Main Components
• If the portfolio website serves as a hub linking to these subprojects, include a top‑level “Portfolio Hub” that centrally connects to the other projects.
• For hivegames-frontend:
• React SPA nature by explicitly including components (Navbar, Footer, GameCard, GameList, and various pages like HomePage, LoginPage, etc.).
• That it uses Vite as a build tool, and there is a clear separation between the “src” (application logic and UI components) and “public” (static assets) directories.
• A “Services/API” component that suggests communication with external back-end services or data sources.
• For the portfolio section: Mark it as a web presentation layer that likely links out to or showcases the mini‑applications.
Relationships and Data Flow
• Client–side data flow: for static apps, one can simply show a user’s browser accessing the HTML/JS/CSS, whereas the React app may have more interactive and asynchronous flows.
Architectural Patterns or Design Principles
• For hivegames-frontend, mention the component-based architecture—a key characteristic of React applications.
• Use a separation-of-concerns principle by making sure that each mini-application is depicted as an isolated layer with its frontend technologies (and backend, if applicable).
• If the portfolio page acts as an aggregator, reflect that with a clear separation between the “presentation layer” (portfolio index) and the “application layers” (each mini‑app).