BekzodIsakov• 100
@BekzodIsakov
Submitted
Cheikh Sy
@chkhs
All comments
- Cheikh Sy• 30
@chkhs
Posted
Semantic HTML: The solution uses semantic HTML elements, which is great for accessibility and SEO. If there are any areas where divs or spans could be replaced with more meaningful tags (like <article>, <section>, or <nav>), consider making those changes.
Accessibility: The use of alt attributes for images, ARIA roles, and proper label associations with form elements is essential. If these aren’t implemented, adding them would improve accessibility.
Responsive Design: The layout looks good on various screen sizes. If media queries or responsive units (like em or rem) aren't used, adding them can enhance the experience on different devices.
Code Structure: The code is well-organized and easy to read. Using comments to explain complex sections can make it even more understandable. Additionally, consider breaking down large components into smaller, reusable ones if applicable.
Design Consistency: If the solution differs from the design, it might be due to intentional improvements or limitations. Ensure any changes are justified and that the core design intent remains intact.
Overall, this is a solid solution with minor areas for enhancement in accessibility and potential code refactoring for reusability. Great job!
0 - TitaHerizo• 70
@TitaHerizo
Submitted
What are you most proud of, and what would you do differently next time?
The use of css flex box. Next time, I'll try with other option and see what is the best way to do it.
What challenges did you encounter, and how did you overcome them?
The main challenge is to replicate the design.
What specific areas of your project would you like help with?
Is the any best practice to write css from the design to the website?
Cheikh Sy• 30@chkhs
Posted
Great job, it looks good.
1
