How kwadjanib/bk works
Main components
• Client (Web Browser): Represents the end user’s browser that requests and renders the HTML pages.
• Static Web Server: Even if not explicitly shown by server-side code, assume the site is hosted (e.g., via GitHub Pages, Apache/Nginx, etc.) that serves the HTML, CSS, and PDF files.
• HTML Pages: Each page (index.html, Contact.html, apropos.html, Mon_CV.html) is a discrete component that gets loaded based on user navigation.
• Stylesheets: The CSS files (CSS-Contact.css, CSS-Acceuil.css, CSS-CV.css, CSS-apropos.css, plus one extra file possibly for common layouts) that define the presentation layer.
• Static Assets: The PDF files, which are important downloadable resources provided to the user.
Establish the relationships and interactions
• The User interacts with the Client (web browser).
• The Browser makes HTTP requests to the Static Web Server.
• The Static Web Server returns HTML pages and associated assets such as the CSS files and PDF documents.
• HTML files reference their respective CSS files to ensure consistent theming per page.
• The downloadable PDF documents may be linked from one or more HTML pages, allowing the user to view or download them.
Architectural patterns/design principles
• Separation of Concerns: Different HTML pages are styled separately with dedicated CSS files.
• Static Content Delivery: The entire application is built with static files, relying only on client-side rendering without server-side dynamic logic.
• Simple, clear navigation paths: Likely a main homepage (index.html) that links to other specialized pages (contact, about, CV) – this might correspond to a basic multi-page navigation structure.
Additional details
Happy diagramming!