How shashikant190/shashikant190 works
Project type and purpose
• This “project” is a single-file GitHub repository hosting a personal README.md.
• Purpose: serve as a developer’s profile page on GitHub, display badges and stats, link out to a resume (hosted elsewhere), and showcase skills and contact info.
File structure
• Top-level: only README.md
• No source directories, no build scripts, no backend code
• External assets are embedded via hotlinked images/badges (shields.io, GitHub-readme-stats, komarev, etc.)
README for additional insights
• No explicit architecture section
• Uses third-party services to render badges, charts, and stats
• Links to an external resume site hosted via GitHub Pages
Main components
a. Developer (You)
b. GitHub Repository (hosted on github.com) containing README.md
c. GitHub Pages / GitHub UI (renders the README when a visitor views the repo)
d. External Badge & Stats Services
• shields.io (profile views, repo size)
• komarev.com (profile visitor counter)
• GitHub-readme-stats API (stats, top-langs, streak)
• GitHub profile avatar and links
e. External Resume Site (https://shashikant190.github.io/Resume/)
Relationships and data flow
• You push updates to README.md → GitHub Repo
• Visitor opens the repo page on GitHub → GitHub UI fetches README.md
• GitHub UI parses markdown, then issues HTTP requests to external services for badges/stats/images
• Browser displays the combined content
• Clicking the resume link redirects visitor to the external resume site
Architectural patterns / design principles
• Static-site hosting (no build or runtime server code)
• CDN and API-driven content embedding
• Client-side composition: browser fetches external assets at page-view time
Final checklist
• Clear node for Developer (authoring)
• Node for GitHub Repository (source of truth)
• Node for GitHub Rendering/UI (serving README)
• Nodes for each badge/stats service
• Node for External Resume Site