How dadiya-harsh-wappnet/dadiya-harsh-wappnet works
Project type and purpose
• This “project” is a personal GitHub profile repository containing only a README.md.
• Its purpose is to display the owner’s bio, GitHub activity stats, top-language breakdown, and contact info as a static, auto-rendered profile page.
File structure
• Top-level:
• README.md (no other directories or code).
• There are no source folders, services, or build scripts—just content and embedded badges/images.
README for additional insights
• Uses third-party badge services (github-readme-stats) to pull dynamic metrics.
• Embeds images from URLs that are generated at runtime by an external stats API (Vercel endpoints).
a. Main components
• Developer workstation (local)
• GitHub repository (profile-repo)
• GitHub Markdown renderer (GitHub UI/backend)
• External Stats Service A (github-readme-stats API)
• External Stats Service B (top-langs API)
• End user (browser)
b. Relationships & interactions
1. Developer edits/commits README.md → pushes to GitHub repo.
2. User navigates to the GitHub profile URL → GitHub backend parses the README, then:
– Calls Stats Service A to fetch the “GitHub Stats” image.
– Calls Stats Service B to fetch the “Top Languages” image.
3. GitHub inlines those images into the rendered HTML and sends it to the user’s browser.
c. Architectural patterns & design principles
• Static-content hosting with dynamic badges (a hybrid static + microservice-driven data fetch).
• Separation of concerns: content (README.md) vs. metrics computation (external microservices).
• CDN/distributed fetch: external APIs likely backed by a CDN or serverless functions.
d. Relevant technologies, frameworks, libraries
• GitHub Markdown renderer
• github-readme-stats (Vercel functions)
• GitHub Pages / GitHub profile hosting mechanism
• Standard HTTPS for badge embedding