Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 26 days ago

Recipe Page Responsive

Farid_Danilo•140
@FaridDanilo
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I'm proud to have made good progress on this new project and to be able to do it as best I could, just like in the preview. I really enjoyed making this design and I'm very proud of having done it.

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

One of the biggest challenges this time was being able to properly adapt the "@media" to fit all existing devices so that it would look good depending on the device where the design is being viewed.

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

This time I don't have any specific area at the moment that requires guidance or help, but I know that I still need to improve and I know that I could further improve the design and the versatility and reduction of code for a more optimal page for everyone. Anything you have to tell me to change or correct, I know that it will be of great help to continue growing and advancing even more.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,320
    @dar-ju
    Posted 26 days ago

    Hi, Farid_Danilo!

    Great job!

    This task can improve the semantics. The way you did it is not a mistake, but it can help search engines and readers understand the page better. Especially search engines, which will index the page better.

    For example, there are headings and subheadings, the name of recipe is the title, use the <H1> tag or higher, instructions and ingredients are the next heading tag in the hierarchy. By the way, the <section> tag requires an h1-h6 heading inside, then you will not have an error using this tag.

    Try to use the div tag for blocks and containers, for text there are p, h, span, strong tags and so on.

    You need to fill in the alt for the image, in the alt describe what you see in the image. Leave an empty alt for decorative and background images that search engines are not interested in.

    Otherwise, everything is fine, good luck with your development!

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