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

Recipe Page using HTML and CSS

P
gregoriusgrd•80
@gregoriusgrd
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

any quick improvement on my css, thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Debarshi Polley•180
    @Dpolley99
    Posted 15 days ago

    The desktop design looks good, you just missed the background-color within the .page-preparation_container.

    Also, if you have been given certain measures in the style guide, try to use them exactly. For example, in the media query, you have used 48 rem instead of doing it in 375px. I would practice avoiding this because in a professional setting, if the design changes, it becomes more difficult to make the changes in the code.

    Also, the mobile design does not have the stone colour in the background. This should be an easy change in the CSS, and there are multiple ways to bring the solution closer to the goal.

    Marked as helpful
  • sttilstra•130
    @sttilstra
    Posted 15 days ago

    This looks great! I see you put the preparation time section in its' own div, but the background color is still the same as the entire page. Updating that should be a straightforward change and get this solution even closer to the goal. Nice work on the nutrition table also. Thank you for sharing!

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

Oops! 😬

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

Log in with GitHub