@giuseppe-giannottaSubmitted about 1 month ago
What are you most proud of, and what would you do differently next time?
Proud of learning to use css grid
Latest solutions
Social-links
Submitted 5 months agoIn the area of responsive design, it is a very interesting area, because the design from desktop to mobile looks almost the same, there are just a few differences.
Latest comments
- @progValjiPosted about 1 month ago
Hi friend, I've taken a look at your code and I think it's incredible, you achieved a good result. I would like to give you some recommendations to improve your code
- remove a bit of gap, this can make it look much better, as well as the design
- use the structure pseudoclasses (:first-child, :last-child, :only-child, :first-of-type, :last-of-type....). This is to avoid creating more classes, it's like another possible solution to give styles to the cards
Marked as helpful0 - P@KaeTheDevSubmitted about 1 month agoWhat are you most proud of, and what would you do differently next time?
I am proud of getting the responsiveness just right, ensuring that the design closely matches the final vision. In my last project, the Recipe Page, I struggled with layout and responsiveness—I got everything looking right, but the structure didn’t quite work as intended. With this project, I’ve learned valuable lessons that I plan to apply when I revisit and improve the Recipe Page project.
What challenges did you encounter, and how did you overcome them?I struggled with deciding whether to approach the design with a mobile-first or desktop-first strategy, as I wanted to avoid the same issues I faced in my last project. At first, getting the mobile layout right without affecting the desktop layout was a challenge. However, I worked through it by carefully adjusting breakpoints and testing the responsiveness at different screen sizes.
What specific areas of your project would you like help with?I took a different approach to handling responsiveness this time, and while I understand that every project requires a unique strategy, I’d love feedback on whether my approach makes sense. I’d also like to know if the techniques I used could be applied effectively in future projects.
@progValjiPosted about 1 month agoHi, I've seen your code and it seems very good. However, I would like to share some of my points of view: The handling of the source tag is quite good, personally I don't use that tag, I only do it with CSS and the help of media-queries. You can do the following: Use <picture> for semantic images that require technical adaptation (formats, density, art direction). Use CSS Media Queries for backgrounds or decorative elements where accessibility is not critical. In modern projects, combine both: <picture> for content and CSS for layout. My last recommendation is that you use BEM, this helps you reuse classes and make your project maintainable in the future.
Marked as helpful0 - @ShamSutherSubmitted 11 months agoWhat specific areas of your project would you like help with?
Nothing actually, but I would really appreciate any feedback😊
@progValjiPosted 2 months agoHi friend, I've seen your code and it seems like a good website, very well adapted. However, I would like to give you some recommendations that I'm sure will help you. *It would be better to maintain a consistent BEM structure For example, instead of .preview-img, it could be .blog-preview-card__image Nested elements like author-name could be .blog-preview-card__author-name *Add visible focus states for all interactive elements
0 - @vitoriarasoSubmitted 5 months ago@progValjiPosted 5 months ago
Hi mate, I've seen your code and it seems very good to me, it's very well structured. But I would like to give you a recommendation that was given to me and I hope it helps you.
Instead of grouping the links in a simple div, what better than grouping them in a nav tag, which gives much more semantic to the code. And apart from that, this helps the attendees of disabled people.
From there on, everything is fine.
Marked as helpful0 - P@jdillard2532Submitted 5 months ago@progValjiPosted 5 months ago
Hi James, I've taken a look at your code and it seems to me to be a good code, with semantics included and well structured. Let me tell you some points where you can improve and do so next time, the result will be amazing. Responsive font adjustment: Consider using clamp() to adapt the size of the fonts depending on the width of the screen.Accessible Hover: The h1:hover changes color to yellow, which is great, but may not be as accessible if the text is on a light background. You could include an additional effect like text-shadow or underline. I congratulate you for completing the challenge.
Marked as helpful0 - @svolodarskyiSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
proud that i knew where to start, what do to and build it in short period of time
What challenges did you encounter, and how did you overcome them?the figma file showed the design for screen width 320. the element sizes are same as for desktop. additionally the design showed margins on the sized which was strange since the card width is 320 and screen width is 320 as well
@progValjiPosted 5 months agoA code exactly the same as the proposed one.
The design looks good on different screen sizes, without any complications. You can use a <main> tag instead of a simple <div> for the main structure it might be more semantic. Also including the alt attribute in the image could be a good choice. Consider defining a fallback font in case the Outfit font does not load.Marked as helpful0
