Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

html css

P
Nikhil•100
@nikxe
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?

awesome stuff

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • sofiasmnk•110
    @sofiasmnk
    Posted 8 months ago

    You probably don't want to be manually setting a height and width in pixels for every element (.container, img, .content). For an instance, the image could've just had it's width set to 100% and it would've adjusted to the size of the container.

    The container appears off-centered to me. I think the margin-left:35%; margin-right: 35%; properties on it are the problem. If you want the margins to adapt so that the content is always centered, you can apply margin: auto. (in this case, where you have 128px set for the margin top and bottom, you could use the margin shorthand to write is all as margin: 128px auto. The first value will be applied to the top and bottom, the second value will be applied to the left and right.)

    The challenged proposed that you try to use semantic HTML. The ul and ol elements for the lists have been applied correctly. There are other places where you could've used semantic elements instead of div:

    • h1, h2, h3 etc. for headings;
    • p for paragraphs;
    • table for the nutrition table.

    Semantic HTML is better for accessibility and for search engine optimization.

    Finally, the design doesn't seem to be responsive. There are a few things you could do to make it responsive:

    • Set max-width rather than width on elements, allowing them to size themselves down in smaller screens.
    • Use margin: auto.
    • Change styles depending on screen size using media queries (ie. @media screen and (min-width: 375px) etc.)

    For this challenge, there's a different design provided for small/mobile screens, which has some differences from the desktop design. You'd probably have to use media queries to achieve that. However, just using more flexible properties and values like max-width and margin: auto should also help a lot to make things more responsive in general.

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