All comments

• 

  Alexandru736• 210

  @Alexandru736

  Submitted 30 days ago

  What are you most proud of, and what would you do differently next time?

  How I managed my first webpage using JS. I am also proud how I managed to insert the json data dynamically into the code. Next time, I might change how I populate the html string. I've look it up that modifying the innerHTML property is security-breach prone, so it might be not safe to use it the same I did this time. I am also proud that through the process of designing the app, I found out about ARIA standards. I would recommend everybody who learns about web accessibility to look it up.

  What challenges did you encounter, and how did you overcome them?

  It was pretty hard for me to understand the interaction between the CSS and HTML, how to add events to the tabs, so that both their state and the panels' states change, and how to do that while fetching the data from json. I overcame this challenge by separate the event handlers to the fetching process. Then, I manipulated the json data and split it into the 3 different timeframes, so that accessing the value would be made more easier in the HTML file. In the end, instead of thinking how to update the HTML string, I generated the 3 different panels in the javascript file.

  What specific areas of your project would you like help with?

  I would love if I would be pointed better solutions for the json data manipulation, so that, if there would be added another timeframe as a tab, the whole process of adding is done easier.

  

  Time-tracking Dashboard using SASS

  1

  11

  

  P

  Flávio Júnior• 100

  @flavin-jr

  Posted 18 days ago

  great job, a little different form the main design, but great work!!!!

  1
• 

  P

  wideirp• 280

  @wideirp

  Submitted about 1 month ago

  

  Email Sign-up with Success Message in HTML, Sass, JS

  1

  10

  

  P

  Flávio Júnior• 100

  @flavin-jr

  Posted 20 days ago

  good job!!

  0
• 

  P

  wideirp• 280

  @wideirp

  Submitted about 1 month ago

  What specific areas of your project would you like help with?

  I would like to add an animation slide in but I don't know much about CSS animations. If you can help me out, I would appreciate it!

  

  Article preview component with HTML, sass and js

  1

  11

  

  P

  Flávio Júnior• 100

  @flavin-jr

  Posted 25 days ago

  1. Does the solution include semantic HTML?

     • Yes, the solution includes semantic HTML. Elements such as <header>, <main>, <article>, and <footer> are used appropriately, providing clear meaning and improving the document's readability and accessibility.

  2. Is it accessible, and what improvements could be made?

     • Yes, the solution is accessible. The use of semantic elements aids screen readers and other assistive technologies in understanding the content and its structure. To further enhance accessibility, consider adding aria-labels or descriptive alt attributes for images.

  3. Does the layout look good on a range of screen sizes?

     • Yes, the layout is responsive. Media queries are employed to adjust the design for different screen sizes, ensuring that it looks good on both large screens and smaller devices. This approach maintains usability and aesthetics across various devices.

  4. Is the code well-structured, readable, and reusable?

     • Yes, the code is well-structured, readable, and reusable. The use of semantic HTML and organized CSS rules contributes to a clean and maintainable codebase. SCSS mixins and variables enhance reusability and consistency, making the styling easier to update and manage.

  5. Does the solution differ considerably from the design?

     • No, the solution aligns closely with the design. The semantic HTML and responsive layout ensure that the design principles are preserved across different devices and screen sizes, effectively translating the design into a functional and visually appealing web page.

  1. Does the solution include semantic HTML?

     • Yes, the solution includes semantic HTML. Elements such as <header>, <main>, <article>, and <footer> are used appropriately, providing clear meaning and improving the document's readability and accessibility.

  2. Is it accessible, and what improvements could be made?

     • Yes, the solution is accessible. The use of semantic elements aids screen readers and other assistive technologies in understanding the content and its structure. To further enhance accessibility, consider adding aria-labels or descriptive alt attributes for images.

  3. Does the layout look good on a range of screen sizes?

     • Yes, the layout is responsive. Media queries are employed to adjust the design for different screen sizes, ensuring that it looks good on both large screens and smaller devices. This approach maintains usability and aesthetics across various devices.

  4. Is the code well-structured, readable, and reusable?

     • Yes, the code is well-structured, readable, and reusable. The use of semantic HTML and organized CSS rules contributes to a clean and maintainable codebase. SCSS mixins and variables enhance reusability and consistency, making the styling easier to update and manage.

  5. Does the solution differ considerably from the design?

     • No, the solution aligns closely with the design. The semantic HTML and responsive layout ensure that the design principles are preserved across different devices and screen sizes, effectively translating the design into a functional and visually appealing web page.

  0