How raju2525/portfolio works
Project type and purpose
• This is a single-page portfolio website built in React.js. Its sole function is to display a personal resume, technical skills, project showcase, and related static assets (PDF, images). There is no custom backend API in the codebase—deployment is via a static-site host.
File structure
• Top-level:
• public/ – contains index.html, manifest.json, robots.txt and other static files served verbatim.
• src/ – React application source, including:
– App.js, index.js, global CSS files
– Assets/ – images, resume PDF
– components/ – React components grouped by feature (Home, About, Projects, Resume, Navbar, Footer, utility components)
• package.json, package-lock.json – declares dependencies and NPM scripts.
• README.md – describes project purpose and dependencies.
• No “backend” or API directories; build and serve are client-side only.
README for additional insights
• Technology stack: React.js, Node.js (for build), Express.js (mentioned but not present in code), CSS3.
• Deployment platform: Vercel (continuous deployment on push).
Elements
• Clear labels:
• “Browser”
• “CDN / Vercel Hosting”
• “React SPA (bundle.js, index.html)”
• “Component Modules (Home, About, Projects, Resume, Navbar, Footer)”
• “Static Assets (PDF, images)”
• “GitHub (Source Control)”
• “Node.js Build Server”
– GitHub push → Vercel build
– Vercel build → CDN deployment
– Browser request → CDN
– CDN → Browser serves index.html & JS
– React app → fetch static assets
Detail and essential elements
• Related components with containers (e.g., one container for “React application” that encloses all component modules).
• Don’t add fictitious modules; reflect exactly the folder structure and actual libraries in package.json.