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

Recipe Page

Aziz•130
@AzizJatoi
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please review the code

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Osman Bay•690
    @osmanbay90
    Posted over 1 year ago

    Great job on completing the Frontend Mentor challenge! Your project shows promise, but here are some areas where you could make improvements in your HTML:

    1. Heading Elements: Ensure you're using heading elements (<h1>, <h2>, etc.) appropriately to provide a clear hierarchy for your content. For instance, you could consider using <h2> elements for subheadings like "Preparation time," "Ingredients," "Instructions," and "Nutrition."

    2. Article vs. Section: You've used <article> elements for each section of content. While this isn't incorrect, consider whether these sections represent standalone, independent content that could be syndicated or bookmarked separately. If not, you might want to use <section> elements instead, which are more generic and represent thematic groupings of content.

    3. Alt Attributes: Ensure all <img> tags have appropriate alt attributes to provide alternative text for screen readers and in case the image fails to load.

    4. CSS Classes: Review your CSS classes to ensure they accurately reflect the content they're styling. For instance, in your <article> elements, the class "Instructions" seems unnecessary since you already have "Instructions" as part of the class name.

    5. Use of <p> for Single Lines: You're using <p> tags for single lines of text in some places. While this isn't incorrect, consider whether a <p> tag is semantically appropriate for these instances. If the text doesn't represent a paragraph of content, you might consider using <span> or <div> instead.

    Remember, practice makes perfect! Keep refining your skills by tackling more challenges on Frontend Mentor. Happy coding! 🚀

    Marked as helpful

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub