Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Flexbox, media Query, p inside list to f create spaces between

Adrian Reina Lobaina•290
@adrian-reina-391
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 only proud of Not Having Given Up

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

Honestly, this was more difficult than other more complex challenges I've done. The worst part was getting a certain amount of space between the bullets and the text of the lists. It took me a long time to find a solution that worked even after having everything else ready. I think it's almost perfect, it looks good on mobile-first and desktop too.

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

...

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • AliAsghar Zare•70
    @iliAsghar
    Posted about 1 year ago

    nice! ✅ I'm already knee-deep in the midst of this challenge. :D making the layout responsive is killing me :)

    some quick notes on your solution :

    • i think you used the wrong color hex for the text elements (not blaming you though , the colors made me insane too 😵‍💫)
    • in your Nutrition List, to add the border-bottoms , you could use :not(:last-child()) to avoid the last row to have a border-bottom
    • for big , heavy projects , developers have a specific Naming convention that they use throughout the designing process . i'm not saying it was necessary for this challange , i'm just saying by using it and sticking to one, you'll learn the Ups and Downs of it and learn to quickly name the elements based on the context. one of my favorite Naming conventions is BEM Naming . you can check that out Here
  • Skalex Stuch•210
    @mussino
    Posted about 1 year ago

    To make the HTML more semantic, you can replace the <div> elements with more appropriate HTML5 semantic elements that better describe the purpose of the content.

    for example using <main> tag is used to wrap the main content of the page.

    <article> tag is used to represent a complete, self-contained piece of content (the recipe). <figure> and <figcaption> tags are used to represent the image and its caption. <section> tags are used to group related content sections (like preparation time, ingredients, instructions, etc.). <h1>, <h2>, <strong>, <ul>, <ol>, and <table> tags are used to provide semantic headings, lists, and tables for better accessibility and SEO. The <footer> tag is used for the attribution section at the bottom of the page.

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