Latest solutions
I used flex box for a mobile screens and grid box for largers screens
Submitted about 1 month agoFor desktop grid display, this property is not solid already.
I used HTML, CSS grid and CSS flexbox for the solution
Submitted 4 months agoI don't have any details that come to mind. However, all observations are welcome because they all add knowledge.
I used HTML and CSS only
Submitted 5 months agoIn this particular project, I need help with the responsive part, especially with text formatting. I couldn't find a way to keep the text at a fixed size while allowing it to break when the screen size decreases. Instead, it reduces proportionally to the screen. I couldn’t identify where I’m making the mistake.
HTML e CSS tools to develop this challenge
Submitted 5 months agoSpecifically, with this website, I am satisfied with the result. But suggestions for improvements are always welcome.
I used HTML semantics tags and I used CSS responsive grid
Submitted 5 months agoI believe my doubts are in responsive solutions. I don't know if it's really good enough.
Latest comments
- @Dhia-zorai@GleberC
Your project has a very good layout! It came very close to what was proposed! The suggestions I can give would be to create a separate stylesheet file; I believe this would make your project look more professional, but it doesn't prevent a good final result. Another suggestion, also to add more professionalism – and I'm not trying to criticize your solution – would be to use more semantic tags, further defining each block beyond just class definitions. These are just code suggestions. As for the resolution of your project, it's very good!
Marked as helpful - @a-2280What are you most proud of, and what would you do differently next time?
I proud of coming up with a solution for this so quickly.
What challenges did you encounter, and how did you overcome them?As usual I just had some sizing issues but those are fixed with trial and error.
What specific areas of your project would you like help with?How did I do?
@GleberCDoes the solution include semantic HTML? In my understanding, it has very good semantics.
Is it accessible, and what improvements could be made? Yes, I consider the accessibility to be appropriate.
Does the layout look good on a range of screen sizes? Yes, the solution for various screen sizes turned out very well.
Is the code well-structured, readable, and reusable? I believe so. Since I used a similar approach, it’s also the way I interpreted it.
Does the solution differ considerably from the design? It’s very close to the proposed design. I believe it achieved the objective very well. - P@socratesioaWhat are you most proud of, and what would you do differently next time?
I managed to complete quite quickly. It was an interesting design and this always gives me inspiration to code.
What challenges did you encounter, and how did you overcome them?Just the <picture> HTML element. I read up on it and its pretty easy to understand yet very powerful and useful.
What specific areas of your project would you like help with?Is the markup and CSS clean? Where should I improve?
@GleberCDoes the solution include semantic HTML? Yes. Very well coded. Is it accessible, and what improvements could be made? I believe it is very accessible, and with the knowledge I have, I couldn't suggest anything beyond what already exists in this code. Does the layout look good on a range of screen sizes? So far, within Frontend Mentor, it’s the best layout I’ve seen—practically perfect compared to the proposed design. Is the code well-structured, readable, and reusable? Yes, the code is very well structured and even gave me some ideas. Does the solution differ considerably from the design? It’s practically identical. Excellent project.
Marked as helpful - @nikhilbleedsblue@GleberC
Does the solution include semantic HTML? I believe the code has good semantics, but for example, in the nutrition part, more semantic tags could be used, such as 'table', 'tr', and 'td'. This way, the code will have better semantics overall.
Is it accessible, and what improvements could be made? As I said, I suggest in the nutrition part, tags such as 'table', 'tr', and 'td'could be used.
Does the layout look good on a range of screen sizes? The differences I noticed compared to the proposal are the measurements in the central element, where the nutritional information is located. But the responsive elements worked very well.
Is the code well-structured, readable, and reusable? Yes, the structure is ok.
Does the solution differ considerably from the design? In my understanding, the measurements of the elements on the page are what I noticed as the biggest differences. But the information is all included, and the styling of the sections is also in accordance.
- P@SidorovaMaria@GleberC
Does the solution include semantic HTML? Yes, the code has a good semantic HTML. Is it accessible, and what improvements could be made? The only thing I noticed is that there is no button that takes you to the link shown in the list. Does the layout look good on a range of screen sizes? The layout is perfect. Is the code well-structured, readable, and reusable? Yes, the tags used let the code very clear. Does the solution differ considerably from the design? The only comment is about the button mentioned earlier.
- @tazzidhum@GleberC
Does the solution include semantic HTML? I believe the site is fine in terms of semantics. Maybe I would include the <main> tag to give the "main" semantic to the site. s it accessible, and what improvements could be made? In my opinion, it is accessible. Does the layout look good on different screen sizes? What I noticed is that the "#preview-card-container" has a slightly greater height than the challenge proposes. Is the code well-structured, readable, and reusable? Yes, I believe the project has a good structure. Does the solution differ significantly from the design? No, I think the project has few differences from the proposed design.