Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Recipe Page Main

Prajwal H Cโ€ข210
@prajwalhc-18
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Olaniyi Ezekielโ€ข7,580
    @Ezekiel225
    Posted over 1 year ago

    Hello there ๐Ÿ‘‹ @prajwalhc-18.

    Good job on completing the challenge !

    Your project looks really good!

    I have a suggestion about your code that might interest you.

    ๐Ÿ“Œ First: Use <main> to wrap the main content instead of <div>.

    Tags like <div> and <span> are typical examples of non-semantic HTML elements. They serve only as content holders but give no indication as to what type of content they contain or what role that content plays on the page.

    ๐Ÿ“ŒIf you don't have the Figma design files, I recommend using a browser extension called Perfect Pixel.

    It allows you to compare your finished project with the design images that come along when you download the project and check the (almost exact) dimensions. It's very useful!

    I hope this suggestion is useful for future projects.

    Other than that, great job!

    Keep up the excellent work and continue to challenge yourself with new projects. Your progress is impressive, and each project is a step forward in your front-end development journey! ๐Ÿš€๐ŸŒŸ.

    Happy coding.

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
ยฉ Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! ๐Ÿ˜ฌ

You need to be logged in before you can do that.

Log in with GitHub

Oops! ๐Ÿ˜ฌ

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up โ€œinvalidโ€ attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although theyโ€™re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! ๐Ÿ˜ฌ

You need to be logged in before you can do that.

Log in with GitHub