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

Recipe Page Made with HTML and CSS (lists, tables)

pure-css
Jsnowoliv1420•50
@Jsnowoliv1420
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?

Esta vez seguí al pie de la letra el diseño (al menos en móvil) y me quedo más parecida, me gustó mucho como quedó mi página.

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

El colocarle el color a las listas y colocarle la negrita

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

En el diseño responsivo

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,930
    @beowulf1958
    Posted about 1 year ago

    Congratulations on completing this challenge.

    There are a few issues with the code. First, the html will not validate. The reason it will not validate is because of the <img /> tag in line 22; all image tags must have an alt attribute. The content of the alt is your explanation of what the image is. For example:

    <img src="image-omelette.jpeg" alt="omelette and toast on a plate">
    
    

    Second, the CSS contains an invalid statement in line 46; there is no such rule as "space-between: 5px; "

    Third the image does not look right. Fourth, the content should all sit in the middle of the page. These two issues are related; fixing one helps with the other. To fix the image problem, replace your <img /> styles with the following. Then add two new lines to the class ".contenedor"

      .contenedor{
        width: 30 rem;
        margin: 0 auto;
        border-radius: 5px;
        background-color:hsl(0, 0%, 100%) ;
      }
      img{
        border-radius:5px;
        display: block;
        width: 100%;
        }
    
    

    After doing this, you should see a big improvement in how the page looks. Hope this helps.

    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

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