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

I0 have used CSS properties to have page responsive

varun kumar•80
@varunKumar993
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?

it was a good project to understand how HTML and CSS works

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

it was a good project to understand how HTML and CSS works

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Krushna Sinnarkar•1,080
    @krushnasinnarkar
    Posted 12 months ago

    Hi @varunKumar993,

    Congratulations on successfully completing the challenge!

    Your solution looks nice, though there are a couple of things you can improve which I hope will be helpful:

    1. Background Colors:

      • The background colors of the body and .container elements do not match the design. Make sure to use the exact colors specified in the design.
    2. Responsiveness:

      • Your website is not responsive below 500px. This issue arises due to the fixed width of 500px given to the .container and table elements. To solve this, you can use max-width instead. This will set a maximum width of 500px for your elements and will automatically reduce the size if the screen size is smaller than 500px.

      Example:

      .container, table {
          max-width: 500px;
          width: 100%;
      }
      
    3. Background Color for .preparation:

      • The .preparation section is missing its background color as per the design. Make sure to add it to match the design specifications.
    4. Font and Font Sizes:

      • Ensure you use the fonts and font sizes given in the style guide to make your solution more accurate to the design.
    5. List Styles:

      • The ul bullets and ol numbers should have specific colors. You can achieve this by using the ::marker pseudo-element.

      Example:

      ul::marker, ol::marker {
          color: #specifiedColor;
      }
      
    6. Layout Using Flexbox:

      • Instead of using margins to separate each section, consider using Flexbox for better alignment and spacing. Flexbox provides a more flexible and efficient way to layout, align, and distribute space among items in a container.

      For more information on Flexbox, you can check out these resources:

      • W3Schools Flexbox
      • MDN Web Docs Flexbox

    I hope you find this helpful. Feel free to reach out if you have more questions or need further assistance.

    Happy coding!

  • Owolabi•250
    @Ay-dotcode
    Posted 12 months ago

    Good job But it doesn't exactly look like what you were told to design

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

Oops! 😬

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

Log in with GitHub