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

Recipe Webpage Built Using HTML + CSS

maggiechua•50
@maggiechua
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?

I'm most proud of the table formatting for this project. It was one of the most challenging parts of this project for me and learning how to structure and style the component was quite rewarding especially once I figured it out. I think for future projects, I want to take more notes on my process as well as figuring out ways to best structure my code, so that it's as efficient and effective as possible.

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

A major challenge I faced was figuring out how to change the colors of the markers for the list items and how to position them so that they weren't so close to the text. That took quite a bit of looking over the web.dev pages and googling for additional resources. I also did some experimentation by playing around with the values until I was satisfied with the spacing.

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

I spent quite a lot of time trying to figure out how to reposition the container after I resized the window, but I wasn't able to figure out how to do it properly. When you resize the window, the recipe page is responsize (so it is readjusted to fit the screen), but there are still margins at the top and bottom that exist that I wasn't able to figure out how to remove. I was using the @media screen query to help me with it, and so it's half working, but not exactly what I want.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Carl•1,235
    @CarlHumm
    Posted 6 months ago

    Hi maggiechua

    Good work on the solution, the bullet points were a tricky part for me as well.

    [ Edit: ] I see your media query isn't working due to ordering.

    "Order of appearance: In the origin with precedence, if there are competing values for a property that are in style block matching selectors of equal specificity and scoping proximity, the last declaration in the style order is applied"

    So your media query is being overwritten by your default styles as they are position after the query.

    Instead, try a mobile first approach to make things easier to organise by writing your default styles first and then adding min-width queries at the bottom for any changes, I find it easier.

    Also, instead of controlling the maximum width using relative margins, you could apply a maximum width to the element and center it using flexbox/grid or the following.

    @media screen and (min-width: 960px) {
     .container {
        max-width: [whatever value you want]
        margin-inline: auto;
      }
    }
    

    Feel free to ask any questions, and keep up the good work!

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