How jainavinash881/abhyaas-yoga works
1. This repository is a single-page React application bootstrapped with Create React App. There is no backend code, API layer, or database in the repo, so the architecture is entirely client-side.
2. The source of truth is the src/ tree. Runtime entry starts at src/index.js, which mounts the React app into the HTML shell and pulls in global styles from src/index.css.
3. src/App.js is the top-level composition layer. It likely wires the shared layout and page selection together, with src/App.css handling app-scoped styling. In a diagram, this is the central UI container above all pages/components.
4. The UI is split into a small number of feature areas:
- src/components/Navbar.jsx for global navigation/chrome
- src/pages/Home.jsx for the landing page
- src/pages/Schedule.jsx for the schedule view
This suggests a simple page-level architecture rather than a deep component hierarchy.
5. The data flow is straightforward: user loads the static HTML shell, React boots from index.js, App renders the shared navigation, and the page components render the visible content. Any screen transitions are handled entirely in the client.
6. There are no obvious external service dependencies in the repository structure. The app appears to be self-contained, with content and assets bundled locally rather than fetched from an API.
7. Static media is part of the app bundle. docs/assets/abhyaas-video.mp4 and files under docs/static/media indicate at least one embedded video asset and some third-party packaged media/fonts. These are served as static files, not generated dynamically.
8. Styling is mostly CSS-based. There are source styles in src/index.css and src/App.css, and the committed docs/static/css/*.css files show production builds with hashed asset names.
9. Testing support is minimal but present. src/App.test.js, src/setupTests.js, and src/reportWebVitals.js are the standard CRA testing/metrics hooks, so the repo includes basic test scaffolding and web-vitals instrumentation support.
10. The public/ directory contains the HTML template and PWA metadata (index.html, manifest.json, robots.txt). These files define the app shell and browser-facing metadata used during build and deployment.
11. The docs/ directory is a committed production build output, not source code. Its hashed JS/CSS bundles, asset manifest, and 404.html strongly suggest the app is deployed as a static site, likely via GitHub Pages or a similar static host with client-side routing support.
12. From an architecture-diagram perspective, the key boundaries are:
- browser/runtime shell versus React application code
- top-level app container versus page components
- source assets versus built static artifacts in docs/
- no server-side boundary, because all behavior is delivered as prebuilt static files
Main entry points: index.js Entry boot · App.js App · docs/index.html Deployed HTML · public/index.html HTML shell
Components 16
Source App
React application source code and styling.
- Entry boot · Bootstraps React and mounts the app into the shell.
src/index.js - App · Top-level composition layer for navigation and page selection.
src/App.js - Navbar · Global chrome and navigation shared across views.
src/components/Navbar.jsx - Home · Landing page content.
src/pages/Home.jsx - Schedule · Schedule view content.
src/pages/Schedule.jsx - Source CSS · App and global styling for the React source.
src/App.css - Global CSS · Base styles loaded at application startup.
src/index.css - CRA tests · Default React test and setup hooks.
src/App.test.js - Vitals hook · Web vitals reporting support from CRA.
src/reportWebVitals.js
Public Shell
HTML template and browser metadata used at build time.
- HTML shell · Root HTML document that hosts the React mount point.
public/index.html - Manifest · Browser metadata and install configuration.
public/manifest.json
Built Site
Committed production build output and static assets.
- Deployed HTML · Published HTML entry for the built site.
docs/index.html - Built bundles · Hashed production JavaScript and CSS assets.
docs/static/js/main.1857ad8c.js - Static media · Committed video and packaged media assets.
docs/assets/abhyaas-video.mp4 - 404 fallback · Client-side routing fallback page for static hosting.
docs/404.html
Other components
- Browser · Loads the static site and executes the client app.
Connections 17
- Browser → HTML shell: loads · The browser requests the HTML shell first.
- HTML shell → Entry boot: mounts · The shell provides the root element for React to attach to.
- Entry boot → App: renders · Entry code boots the top-level app.
- App → Navbar: includes · Shared navigation is composed at the app root.
- App → Home: shows · One of the main client-side views.
- App → Schedule: shows · One of the main client-side views.
- Entry boot → Global CSS: imports · Global styles are loaded during boot.
- App → Source CSS: imports · App-scoped styling supports the root UI.
- Entry boot → Vitals hook: hooks · Startup wiring includes web-vitals reporting.
- Entry boot → CRA tests: supports · Standard CRA test setup accompanies the entry layer.
- HTML shell → Manifest: references · The template links browser/PWA metadata.
- Browser → Deployed HTML: loads · The deployed site is served as static HTML.
- Deployed HTML → Built bundles: includes · Published HTML pulls in hashed build assets.
- Deployed HTML → Static media: embeds · Static media is shipped with the deployed bundle.
- Deployed HTML → 404 fallback: fallback · Static hosting uses a fallback page for client-side routes.
- HTML shell → Deployed HTML: builds to · Source HTML template becomes the deployed HTML during build.
- Entry boot → Built bundles: compiles to · React source is emitted into production bundles.