Submitted 2 months ago

Recipe page

Xavier O.•80

@XavOli

Preview site View code

This is a solution for...Recipe page

HTML
CSS

1newbie

Design comparison

SolutionDesign

Solution retrospective

What are you most proud of, and what would you do differently next time?

Added some responsivity for larger screens as the example provided was only for a screen with narrower width than height. This is why my submitted solution will likely be very much wider than the solution comparison. If you open the published site you'll be able to see better.

What challenges did you encounter, and how did you overcome them?

This is only my second project with bootstrap, I am still figuring a lot of things out.

What specific areas of your project would you like help with?

If there are areas where I can save some time by dividing or organizing differently. I'll try to implement some SASS instead of CSS to correct bootstrap in the future as nesting styles would've been really useful.

Community feedback

Steven Stroud•11,910
@StroudyPosted 2 months ago
Hello again, fantastic effort on this! You’re really nailing it. Just a few things I noticed that could make it even better…

Using a <main> tag inside the <body> of your HTML is a best practice because it clearly identifies the main content of your page. This helps with accessibility and improves how search engines understand your content.

This does not matter that much at this stage but something to be mindful of for SEO(Search Engine Optimisation), <meta> description tag missing that helps search engine determine what the page is about, Something like this <meta name="description" content="description goes here" />

For future project, You could download and host your own fonts using @font-face improves website performance by reducing external requests, provides more control over font usage, ensures consistency across browsers, enhances offline availability, and avoids potential issues if third-party font services become unavailable. Place to get .woff2 fonts

Using !important is not recommended because it overrides all other styles, making debugging and maintenance difficult, causing conflicts, reducing flexibility, and limiting the ability to create scalable, modular CSS.

Using rem or em units in @media queries is better than px because they are relative units that adapt to user settings, like their preferred font size. This makes your design more responsive and accessible, ensuring it looks good on different devices and respects user preferences.

I hope you found this advice helpful! Keep up the great work, You’re doing amazing, and I can’t wait to see what you create next. Happy coding! 🚀
0

Please log in to post a comment

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord