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

Main page using CSS

accessibility
ed•40
@Barcode77
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?

First i most proud that I took the challenge and saw through it. Applying lessons learnt in real life provided a challenging but real way to learn.I also plan to observe time, ie take time off, if needed when in the thick of it

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

Writing HTML and CSS I was a bit familiar with but applying and deploying are new things i got to encounter. Despite what i knew, i realized there was a lot more to cover and get hands on experience on, especially with CSS. By testing different ideas, I deduced the which paths to take, and for deploying, I simply just had to learn.

What specific areas of your project would you like help with?
  1. Extending the color to include the list numbers
  2. Styling the table as provided.
  3. Any other feedback is welcome ; ).
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hitmorecode•7,540
    @hitmorecode
    Posted 7 months ago

    I took a look at what you did. Here are a few thing you can do to improve your page.

    • Let's start with CSS reset. Make it a good habit in applying CSS reset in your page. Here is a simple example of a CSS reset.
    * {
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    }
    
    • After applying CSS reset you don't have to add margin: 0; or padding: 0;.
    • If you want the page to have 100% height, it's best to do it like this min-height: 100vh;.
    • You don't to add width: 100%' on the body. By default the body is always 100%.
    • Avoid giving classes or id's the same name as elements. Don't use body for a class name.
    • I don't understand why you used position relative.
    • You have justify-content: center; without using flexbox.
    body {
        /* margin: 10px auto; */
        /* justify-content: center; */
        background-color: hsl(30, 54%, 90%);
        display: flex;
        justify-content: center;
        align-items: center;
    }
    
    • As you can see the image is not centered, make these changes to fix this.
    img{
        height: 300px;
        /* max-width:600px; */
        border-radius: 15px;
        /* min-width: 375px; */
        width: 100%;
    }
    
    • When you have a font that's going to be used in multiple places, you can just add it on the body.
    • You did not used media query to make the page responsive.
    • Some fonts don't match the design.

    See if you can fix these things and if you need help let me know.

    I hope you find this helpful. Keep it up 👍👌

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