How hidravneno/temperature works
Main Components
• User Interface (HTML/CSS):
– Pages: Include all the HTML files (index.html, Assignment2.html, Assignmnt1.html, activity.html, convert temperature.html, convert-temp.html) as separate UI components.
– Styling: Represent the various CSS files (mystyle.css, style.css, stylees.css, styles.css) that define the look and feel across pages.
• Client-side Logic (JavaScript):
– Scripts: Illustrate the directory “scripts” which holds several JavaScript files (e.g., Assignment1.js, Assignment2.js, Conditional.js, Function-challenge.js, Functions.js, activity1.js, convert temperature.js, convert-temp.js, script.js).
– Explain that these JS files provide interactive functionality, such as temperature conversion calculations and handling user interactions.
• Resources:
• Supporting Documentation/Content:
– Other files such as notes.txt can be depicted as supplementary documentation or references aiding the project’s development.
Relationships and Data Flow
• User Interaction Flow:
– Connect CSS files to the HTML components, noting that style influences presentation but does not directly interact with the logic.
• Script Interactions:
Important Architectural Patterns/Design Principles
• Separation of Concerns:
• Modular and Reusable Components:
– Since multiple assignment or conversion components are spread out as different files, indicate potential grouping or modularity (e.g., grouping similar assignment-related scripts or conversion functionalities).
• Static Frontend Architecture:
– Illustrate that this is a static website with client-side dynamic behavior, with no explicit backend services.
Relevant Technologies
• HTML5, CSS3, and Vanilla JavaScript for the construction of the user interface and interactive elements.
Elements
• Use clear and descriptive labels for each component (e.g., “Index Page”, “Temperature Conversion Page”, “Assignment Functionality”).
– Rectangles for HTML pages
– Ovals or circles for JavaScript modules
– Rounded rectangles for CSS/style elements