How tilak9737/my-portfolio works
Core architectural components
Even a simple static site can be broken down into discrete pieces for clarity:
a. Source Code Repository
• Holds HTML, CSS, JS, images.
b. Continuous Integration / Continuous Deployment (CI/CD)
• Automated build and deploy pipeline (e.g., GitHub Actions, GitLab CI, Netlify Build).
c. Static File Hosting / CDN
• Serves the compiled assets worldwide (e.g., GitHub Pages, Netlify, AWS S3 + CloudFront).
d. End‐User Browser
• Makes HTTP(S) requests, renders the portfolio.
e. Optional Third-Party Services
• Contact Form backend (Formspree, Netlify Functions), Analytics (Google Analytics), Fonts/CDN for libraries.
Relationships and data flows
• Developer → Push to Repo → CI/CD → Deploy artifacts → Hosting/CDN → Browser
• Browser ↔ Third-Party Service (for forms or analytics)
Architectural patterns and principles
• “Jamstack” approach: pre-built markup served over a CDN
• Single Responsibility: CI/CD only builds/deploys; hosting only serves static assets
• High availability via CDN caching; low latency
Putting it all together (sketch outline)
[ Developer Workstation ]
↓ git push
[ Source Code Repository ]
↓ triggers
[ CI/CD Pipeline ]
↓ build & deploy
[ Static Hosting / CDN ] ←──── Browser
│ │
└─→ [ Form Service ] └─→ Analytics