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

recipe page with A lot of semantic html

f1r3•140
@f1r3place
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 love how it behaves at different sizes, just looks and feels awesome

While I would rather not deal with lists ever again in my life, I could probably make the unordered lists look decent using only the ::marker pseudo-element instead of ::before like I did

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

The padding on the lists just did not want to work, at all. Had to look it up, and found a whole article on marker behavior with padding, so that helped

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roberts P•120
    @indaqoo
    Posted 12 months ago

    Hi @f1r3place

    Project looks solid, html is decent, but you could improve some thing about css.

    The current CSS class .container can be improved by separating it into two distinct classes: .container and .card. This approach enhances modularity and reusability.

    Instead of adding a border on an element for horizontal line you could use <hr> element and style it accordingly.

    hr {
        height: 1px;
        background-color: var(--stone-150);
        border: none;
    }
    

    Looks like you are making a lot of flex box container where they are not really needed. since you can apply margin bottom to the heading. and If you could rename divs to sections it would be easy to contorl that

    section > h2 {
        font-family: 'Young Serif', serif;
        font-weight: 400;
        font-size: 1.75rem;
        margin-bottom: var(--size-300);
        color: var(--brown-800);
    }
    

    This is how I styled my lists:

    ul, ol {
        padding-left: var(--size-300);
    }
    
    ol li::marker, ul li::marker {
        color: var(--brown-800);
    }
    
    ol > li::marker {
        font-weight: 500;
    }
    
    li {
        margin-bottom: var(--size-100);
        padding-left: var(--size-200);
    }
    

    There is also some differences in font weights from the design

    Usefull video for lists:

    • How to create and style lists with HTML and CSS
    Marked as helpful
  • Yasser Harzelli•80
    @ItsYasser
    Posted 12 months ago

    good job, header could be less bold

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