How francesco-s/francescosannicola works
Project type and purpose
• This is a static, framework-free personal portfolio website.
• Purpose: showcase projects, articles, résumé; globally deliver via CDN; maintain with minimal overhead.
Main components
a. Development environment (local machine)
b. Source repository (GitHub)
c. CI/CD pipeline (GitHub Actions workflow in .github/workflows/main.yml)
d. Artifact storage and hosting (AWS S3 bucket)
e. Content Delivery Network (AWS CloudFront)
f. End users (browsers on mobile/desktop)
Relationships and interactions
1. Developer edits HTML/CSS/assets locally and pushes to GitHub.
2. Push to main triggers GitHub Actions: lints, builds (trivial for static), and packages files.
3. Workflow synchronizes artifacts to an S3 bucket.
4. After upload, CloudFront invalidation runs to purge edge caches.
5. End users request pages; CloudFront serves cached assets or fetches from S3.
Architectural patterns and design principles
• Static-first: no backend servers or runtime frameworks.
• CI/CD: automated testing and deployment.
• Global CDN: low latency and high availability.
• Edge cache invalidation: ensures fresh content after each deploy.
Step-by-step guidance
• Top: Development & Source Control
• Middle: CI/CD
• Bottom: Hosting & Delivery
e. In the hosting tier, connect “CloudFront CDN” to “S3 Bucket” (cache miss retrieval).
Callouts for important files and folders
• .github/workflows/main.yml (CI config)
• index.html, about.html, style.css (static assets)
• /articles, /projects, /assets directories
• Near “CloudFront CDN,” note: global edge caching & invalidation on deploy.