How shegezzy/olusegun-akinnola-portfolio works
Main Components
• Web Pages: The core HTML files (index.html, 404.html) that serve as the entry points.
• Assets: This includes subdirectories for CSS (styles.css), JavaScript (main.js), images (favicons, portfolio images, skills, etc.), and PDFs (resumes/CVs, etc.).
• Public Folder Components: Files present in the public folder, including a copy of assets, manifest.json (for PWA configuration), and serviceworker.js to enable offline functionality.
• Service Worker: There are serviceworker.js files (both at the root and in public) that enable a progressive web app (PWA) experience.
Visualizing Relationships and Interactions
• Central Component: The web pages (index.html and 404.html) are the primary entry points.
• Asset Loading: Illustrate that the HTML pages load CSS, JavaScript, and image assets from the assets (or public/assets) folder.
• PWA Enhancements: Show that the manifest.json and serviceworker.js work in tandem to support offline capabilities and potentially caching behavior.
• Static Contenting: Emphasize that this project doesn’t have dynamic server-side components; rather, it is designed as a static site with prebuilt resources ready for deployment.
Architectural Patterns/Design Principles
• Separation of Concerns: Clearly separate the static content (HTML/CSS/JS) from the service worker and PWA support files.
• Progressive Enhancement: The inclusion of a service worker and manifest supports a mobile-first and offline-capable design.
• Asset Organization: The structure indicates a logical separation of assets (CSS, JS, images, etc.), which reflects good practices in asset management for static sites.
Relevant Technologies
• HTML, CSS, JavaScript: Core technologies for building the front end.
• Service Workers & Web Manifest: Key for enabling PWA features.
• No Backend or Database: Since this is a static portfolio website, focus on the client-side architecture.