How ketankapale/portfolio works
1. This repository is a Vite-powered React single-page experience, not a traditional multi-page app. The architecture is centered around a single app shell in src/main.jsx and src/App.jsx, with most of the visual logic split into composable scene and UI components.
2. The top-level runtime boundary is:
- src/main.jsx bootstraps React into index.html
- src/App.jsx acts as the composition root
- global styling is split between src/index.css and src/App.css
This makes the app a client-rendered frontend with Vite handling dev server, bundling, and static asset serving.
3. The component structure suggests a highly visual portfolio/landing page. src/components/Ketan.jsx is likely the primary identity/hero element, while Skillset.jsx, Upgrade.jsx, and Upgrades.jsx indicate content sections or interactive presentation of capabilities and achievements.
4. The repository also has a strong “scene” subsystem. Components such as Scenery.jsx, Trees.jsx, Bird.jsx, Butterfly.jsx, and Coffee.jsx imply decorative or animated elements layered into the page. These are likely responsible for the environment and motion that make the experience feel more like an interactive diorama than a standard website.
5. LoadingScreen.jsx and ErrorBoundary.jsx define the app’s resilience boundaries. The loading screen suggests that some assets or scene elements are expensive to initialize, while the error boundary isolates failures in the visual/3D portion so the whole app does not crash if a model or animation fails.
6. Static media is a major part of the architecture. The public/walking/Strut Walking.gltf and public/walking/buffer.bin files indicate a glTF model with external binary data, likely loaded at runtime as part of the scene. The public/cv/KetanKapaleUpdated.pdf file is a downloadable resume asset, separate from the React bundle and served directly as static content.
7. The public directory also contains manifest.webmanifest, robots.txt, and sitemap.xml, which means the site is treated as a deployable public-facing portfolio with PWA/SEO considerations. These files are part of the deployment boundary rather than application logic.
8. index.html is the Vite HTML entry point, and vite.config.js defines build-time behavior and dev tooling. The project includes eslint.config.js, showing code quality is enforced at the source level. package.json and package-lock.json define the app’s JavaScript dependency graph and deterministic installs.
9. netlify.toml indicates the deployment target is Netlify. That matters architecturally because the app is built as a static frontend and hosted on a CDN-backed platform, with routing/redirect behavior likely controlled through Netlify config rather than a custom server.
10. The data flow is mostly one-way and client-side: React mounts the app, App assembles the scene and content components, the components render layered visuals and portfolio content, and external assets are fetched from public/ at runtime. There is no evidence of a backend API, database, or server-side business logic in this repository.
11. In diagram terms, the key boundaries are:
- build/runtime: Vite + React
- composition: App.jsx
- presentation/animation: the scene and character components
- static asset delivery: public/
- resilience: loading and error handling
- deployment: Netlify/CDN hosting
12. Overall, this is best modeled as a static, client-rendered portfolio site with rich visual composition, runtime-loaded media assets, and deployment-oriented public files for SEO, PWA metadata, and downloadable documents.
Main entry points: App.jsx App.jsx · Scenery.jsx Scenery · index.html index.html · main.jsx main.jsx
Components 21
Runtime & build
Vite entrypoint and client-side bootstrap boundary.
- index.html · Vite HTML entrypoint that mounts the React bundle.
index.html - main.jsx · Client bootstrap that renders React into the page.
src/main.jsx - vite.config.js · Build and dev-server configuration for the Vite app.
vite.config.js
Shell & styling
Application composition root and global styles.
Content sections
Portfolio identity and capability sections.
- Ketan · Primary personal/hero presentation for the portfolio.
src/components/Ketan.jsx - Skillset · Capability and technology presentation section.
src/components/Skillset.jsx - Upgrade · Content block for an individual upgrade or milestone.
src/components/Upgrade.jsx - Upgrades · Collection view for progress, highlights, or updates.
src/components/Upgrades.jsx
Scene system
Decorative and animated environment elements.
- Scenery · Coordinates the layered decorative environment.
src/components/Scenery.jsx - Trees · Background terrain and natural scene elements.
src/components/Trees.jsx - Bird · Moving scene element that adds life and motion.
src/components/Bird.jsx - Butterfly · Small decorative motion element in the scene.
src/components/Butterfly.jsx - Coffee · Ambient prop used to reinforce the portfolio mood.
src/components/Coffee.jsx
Resilience
Loading and failure boundaries for expensive visual assets.
- LoadingScreen · Fallback UI while heavy visuals or assets initialize.
src/components/LoadingScreen.jsx - ErrorBoundary · Isolates failures in the visual experience.
src/components/ErrorBoundary.jsx
Static assets & deploy
Public runtime assets and deployment-oriented files.
- Walking Model · glTF model loaded at runtime; uses an external binary buffer.
public/walking/Strut Walking.gltf - Resume PDF · Public CV document served directly from the site.
public/cv/KetanKapaleUpdated.pdf - PWA Meta · Manifest and crawl metadata for deployment and discovery.
public/manifest.webmanifest - netlify.toml · Netlify deployment and routing configuration.
netlify.toml
Connections 20
- index.html → main.jsx: loads · HTML entry loads the React bootstrap.
- main.jsx → App.jsx: renders · Bootstrap mounts the app shell into the DOM.
- App.jsx → LoadingScreen: shows · App coordinates the loading state for heavy initialization.
- App.jsx → ErrorBoundary: wraps · App is protected by a visual error boundary.
- App.jsx → Ketan: composes · Shell assembles the hero identity section.
- App.jsx → Skillset: composes · Shell assembles the skills content section.
- App.jsx → Upgrades: composes · Shell assembles the upgrades/achievements section.
- Upgrades → Upgrade: contains · The upgrades collection renders individual cards.
- App.jsx → Scenery: composes · Shell includes the decorative scene layer.
- Scenery → Trees: layers · Scene compositor includes background environment.
- Scenery → Bird: layers · Scene compositor includes animated bird motion.
- Scenery → Butterfly: layers · Scene compositor includes animated butterfly motion.
- Scenery → Coffee: layers · Scene compositor includes ambient prop styling.
- App.jsx → App.css: styles · Main shell pulls in component-scoped styles.
- App.jsx → index.css: styles · Main shell depends on global baseline styles.
- Scenery → Walking Model: loads · Scene runtime fetches the glTF asset during render.
- App.jsx → Resume PDF: links · Portfolio content exposes the downloadable resume.
- App.jsx → PWA Meta: publishes · Deployment uses public metadata and crawl files.
- vite.config.js → index.html: serves · Vite config governs how the entry page is built and served.
- netlify.toml → index.html: hosts · Netlify hosts the built static frontend.