How raghavendram3/portfolio works
Project type and purpose
• This is a purely static, client-side portfolio website for Dr. Raghavendra Meena, served (most likely) via GitHub Pages or another static-host provider.
• It showcases an “About Me” landing page, academic publications, a photography gallery, and a CV, built entirely from HTML, JSON, images, and PDF files.
File structure
Top-level files and directories:
• CNAME – custom domain configuration (GitHub Pages)
• README.md – project overview and navigation structure
• index.html, cv.html, photography.html, pubs.html – core HTML pages
• images/ – static photo assets, with subfolders “fulls” and “thumbs”
• images.json – metadata manifest for the gallery
• publications/ – PDF documents for each paper
Key observations:
• No server-side code or build scripts—pure static hosting.
• Content segmentation by directory: HTML pages at root, static assets under images/ and publications/.
• CNAME implies DNS integration and static hosting.
README for additional insights
• README outlines the four major “modules” of the site: About Me (Home), Publications, Gallery, CV.
• No mention of a JavaScript framework or build pipeline.
• Content is hand-curated and linked via plain HTML references and JSON for gallery data.
Detail without over-complication
• Directories and file roles (HTML vs. assets vs. metadata).
• Contact point: DNS lookup, HTTP requests for HTML, images.json, images, PDFs.
• Use annotations to note “no backend” and “static content.”
• By layers:
• Content layer (HTML + assets)
• Hosting layer (GitHub Pages + CDN + DNS)
• Client layer (Browser)