Latest solutions
Responsive testimonial grid section
PSubmitted about 2 months agoThe bottom space on Daniel Clifford and Patrick Abrams is too much on the desktop version and i have tried severals ways to reduce it but it is still not working yet, hence why i need help in that area.
Responsive four card feature section
PSubmitted about 2 months agoFor this project, i cannot pinpoint areas where i need help but i am open and hoping for those constructive feedbacks from the community.
Responsive SocialLink Profile
PSubmitted 3 months agoWhen i hover on the social-links link, the hover state moves the whole element and which i guess is not right
Responsive Blog Preview using HTML and CSS
PSubmitted 4 months agoI tried to reduce the avatar image size but to no avail. my subconcious mind kept telling maybe it was because it's in SVG format. i am open to correction tho!
Latest comments
- @XaramsonP@Tech-Badhead
-The code is semantically structured and responsive.
- Always look to apply the the font type given in the style-guide as opposed to the one you used. Typography is just as important as how responsiveness is.
- You pushed all the files given in the starter file to your remote repository which i believe it's not suppose to be like that. What you should do is edit the readme template file to how you approach your project, then safe the changes and rename the readme-template to readme.md then delete orginal readme file. Go through the readme file thoroughly and everything i am saying will make sense.
- @cadanieldevWhat specific areas of your project would you like help with?
display grid
P@Tech-Badhead- The code is responsive and the solution looks like the design.]
- The code is not well structured semantically
- i recommend using browser dev tools (like Chrome DevTools → Layout tab) to debug grid lines.
- @LIFONGHANGP@Tech-Badhead
- The solution is close to the design but attention was not really on the detail which is highly essential in frontend development
- For accessibility best practise, the solution is not semantically structured and semantic HTML thrives well in that aspect.
- The solution does not really look good on various mobile devices, making apps look good on all screen sizes is one of the core fundamentals aspect of frontend development.
- Always look to import the font type given in the style guide of your project, it looks negligible but typography is just as important as responsiveness.
- You are doing awesome and one of the best way to get good is getting hands on building projects like this, keep going and improving along the way.
- P@Tech-BadheadWhat are you most proud of, and what would you do differently next time?
I am proud of myself with the way i tackle things one after the other in completing the project.
What challenges did you encounter, and how did you overcome them?The problem i encountered was the border beneath the table row in the last section and to be honest, i overcome it through try by error!
What specific areas of your project would you like help with?The row bottom border in the nutrition section
P@Tech-Badhead- The solution include semantic HTML
- It is accessible however there will always be room for improvements. I cannot point what improvements could be made at the moment, hopefully when i up my level a bit.
- The layout look good on a range of screen sizes but there still improvements to be made because i only set media queries for 576px. 1.e (max-width: 576px)!
- The code is well structured, readable, and it would have been much better in terms of reusability if i had consider using the css custom properties for the colors used in the project.
- The solution does not differ from the design.
- P@austin-jonasP@Tech-Badhead
Accessibility best practice: -Using semantic tags is a best practice for accessibility. i.e the main tag would have been better in place of the div tag.
- The project does not look good on a range of mobile devices.
- consider using rem, em, and % unit for sizing instead of pixels as it helps scale your work smoothly
- The solution is close to the design for the desktop version
- @Luizf-devdiasWhat are you most proud of, and what would you do differently next time?
Me orgulho de ter feito rápido e bem feito e saber que agora posso sair de novato e tentar projetos juniors.
What challenges did you encounter, and how did you overcome them?Dei uma travada no hover, pesquisei nos meus resumos e consegui resolver
What specific areas of your project would you like help with?Em nenhuma consegui fazer o código bem semântico e organizado
P@Tech-BadheadI've got to be honest, i didn't see any area i can point out for him to improve instead i personally was the one that learnt off his project reading through his code. This are key things i noted from his work: -It is responsive -it is semantically structured -codebase is as tidy as already laid bed -so yeah onto the next! 👍
Marked as helpful