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

Responsive Recipe Page Using CSS Flexbox and Grid

P
Coco•60
@cocoelizabeth
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 am most proud of how I implemented the custom list styles that not only matched the Figma design but are also reusable.

Next time, I would explore incorporating a CSS framework for faster styling.

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

Initially, I was having trouble figuring out how to add custom styling to the list markers and numbers. After doing some research, I discovered CSS counters, which I leveraged to create the custom styles for the ordered lists.

I then realized that all of the lists in the project (Preparation time, Ingredients, and Instructions) had many properties in common (i.e. layout, size, padding, etc), and restructured my HTML lists uniformly and applied a custom, reusable class, .list, to all <ol> and <ul> list elements within the project.

Here's how the HTML structure was standardized:

<!-- For numbered lists -->
<ol class="list custom-ol">
  <li class="text-preset-4 m-b-100"><span>List Item Text</span></li>
  <!-- Additional list items -->
</ol>

<!-- For bulleted lists -->
<ul class="list custom-ul">
  <li class="text-preset-4 m-b-100"><span>List Item Text</span></li>
  <!-- etc. -->
</ul>

In my CSS, I removed default list styling in my css-reset.css, and the .list class that I created in my styles.css defined the consistent base styles for all lists.

/* styles.css */
.list {
    margin: 0;
    padding: 0;
    width: 100%;

    li {
        display: flex;
        width: 100%;
    }

    li::before {
        font-weight: bold;
        color: var(--color-rose-800);
        height: 100%;
        min-width: var(--spacing-500);
        padding-left: 8px;
        padding-right: 8px;
        box-sizing: border-box;
    }
}

/* css-reset.css */
ol,
ul {
  list-style: none;
}

For ordered lists, I created a class called .custom-ol and used the counter-reset and counter-increment properties to number each item uniquely. I also used the content property to append a period after each number.

.custom-ol {
    counter-reset: css-counter;

    li {
        counter-increment: css-counter;
    }

    li::before {
        content: counter(css-counter) ".";
    }
}

For the unordered lists, I created a class called .custom-ul, and adjusted the content to property to display a bullet point. I also utilized Flexbox by adding align-items: center; to ensure that the bullets were centered vertically to each block of text.

.custom-ul {

    li {
        align-items: center;
    }
    
    li::before {
        content: "•";
    }
}
What specific areas of your project would you like help with?

Nothing specific, I think I have a good grasp of the concepts that are covered in this Getting Started learning track and I am ready to move on to more advanced challenges. That being said, any feedback is always welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nader Ashraf•50
    @iNader98
    Posted 5 months ago

    yes yes yes yes no

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