sahrior/cryptex

1. Repository shape

- This is a single-page React dashboard for crypto market data, built as a client-side app with Vite. There is no backend service in the repo; all market data comes from an external API.

2. App bootstrap

- index.html provides the mount point.

- src/main.jsx is the entry entrypoint that renders App.jsx into the DOM.

- src/index.css is the global styling layer for the entire UI.

3. Top-level composition

- src/App.jsx is the app shell that ties the pages together.

- Given the presence of Home.jsx and CoinDetail.jsx, the app is organized around two main screens: a market overview and a coin-specific detail view.

4. Page boundaries

- src/pages/Home.jsx is the list/dashboard view: it likely handles the main market table/cards, search, sorting, and summary display.

- src/pages/CoinDetail.jsx is the drill-down view for a single cryptocurrency, where price trend and deeper statistics are shown.

5. Reusable UI components

- src/components/CryptoCard.jsx is a shared presentational component for displaying coin summary data.

- This suggests the home/list view is composed from repeated cards or rows rather than hardcoded markup.

6. API boundary

- src/API/coinGecko.js is the dedicated integration layer for CoinGecko.

- This isolates HTTP/fetch logic and API endpoint details from the React pages, making the UI depend on a small data-access module instead of calling the API directly everywhere.

7. Data formatting layer

- src/utils/formatter.js handles display-oriented transformations such as currency/number formatting.

- This is an important boundary because it keeps raw API data separate from user-facing labels and localized numeric presentation.

8. Data flow through the app

- The usual flow is: CoinGecko API → API module → page component state → shared card/detail components → formatted UI.

- Home likely consumes a broader market list, while CoinDetail consumes coin-specific metadata and historical trend data.

9. Feature-driven architecture

- The README describes search, sorting, time-range trends, and responsive charts. Architecturally, that means the app is mostly a data-fetch + transform + render pipeline, with interactive filtering/sorting in the page components.

- Chart rendering is part of the page-level presentation, not a separate service boundary.

10. Static assets and public files

- src/assets holds imported images/icons used by components.

- public is for static files served directly by Vite without bundling.

11. Technology boundaries

- The app is built with React + JavaScript + CSS and optimized for fast local development and production bundling via Vite.

- No server, database, authentication, or persistent storage layer is present in the repo structure.

12. Architecture summary

- The repo is a frontend-only crypto dashboard with a clean separation between:

- API access (src/API)

- page-level orchestration (src/pages)

- reusable display components (src/components)

- display formatting helpers (src/utils)

- global app bootstrap/styling (main.jsx, App.jsx, index.css)