How bonolo2s/portfolio-website-2 works
Project type and purpose
• This is a static portfolio website (“Portfolio-website-2”) whose goal is to showcase a personal CV, client testimonials, and other assets. There is no backend or database—just HTML, CSS, JavaScript, PDF files, and static asset folders.
File structure
• Top-level files:
• index.html (entry point)
• main.js (client-side behavior)
• styles.css (presentation)
• Bonolo Selowa Cv.pdf & Curricullum vitae.pdf (downloadable resumes)
• README.md (project title)
• Directories:
• Client testimonials (contains gift.html for individual testimonial page)
• There are no server-side scripts, configuration files, or build tools—this is purely front-end.
README
• Contains only the project name. No extra architecture info or dependencies to document.
Components
a. User’s Web Browser
• Renders index.html, loads CSS and JS, displays PDFs and testimonial pages.
b. Static Web Server or Hosting Service
• Serves index.html, main.js, styles.css, PDFs, and files in assets/ and Client testimonials/.
• Could be GitHub Pages, Netlify, S3+CloudFront, or any CDN.
c. CDN or Asset Delivery (optional)
d. External Services (optional)
Relationships and data flows
• Browser requests → Web Server: “GET styles.css, main.js, /assets/*, /Client testimonials/gift.html, PDFs”
• If using CDN: Web Server or Browser → CDN: “fetch images/fonts”
• Browser renders and displays content to the user.
Architectural patterns and design principles
• Static site architecture (no runtime server logic).
• Separation of concerns: HTML for structure, CSS for styling, JavaScript for interactivity, PDFs and HTML in separate folders for content distribution.
• Keep assets in a dedicated folder to simplify caching and CDN distribution.