Barak Inbal
@BrkCoderAll comments
- @slackwareeSubmitted 7 months agoWhat are you most proud of, and what would you do differently next time?@BrkCoderPosted 4 months ago
Yes this solution include semantic html Yes it is accessible yea the layout look amazing in different screen sizes the code is less readable , the author use only tag selectors without class selectors yea this solution is close to design very much
This solution is well design and can cosider one of the best but I would like to know why to choose tag selectors over class/id selectors? it is less reusable when we choose such approach
0 - @shivani1410551Submitted 6 months ago@BrkCoderPosted 4 months ago
Yea it is include semantic HTML it is accessible it is look good on a range of screen sizes the code is well structured and readable it is a little bit different from the original design in terms of sizing
0 - @fatemzhSubmitted 4 months agoWhat are you most proud of, and what would you do differently next time?
I am most proud of using better Sass techniques, including variables and mixin functions, which significantly improved the maintainability and readability of my code. This experience has given me more confidence in using Sass, and I look forward to utilizing more of its advanced features in future projects.
What challenges did you encounter, and how did you overcome them?No particular ones.
@BrkCoderPosted 4 months agoThis solution include semantic HTML it is accessible it is look good on range of screens it is readable and well structured but the solution is different from design in terms of over size of the card
0 - @namrataachSubmitted 4 months ago@BrkCoderPosted 4 months ago
I don't see any semantic html for accessibility you should less div elements and consider one main instead of wrapper div the layout use grid css which is perfect for range of screen sizes the code is well structured and in terms of readability , the code is simple and readable. the solution is different in dimensions from the original design
0