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

Responsive recipes web created with Html and SASS

sass/scss
LucaRiver0n•10
@LucaRiver0n
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 proud of me becasue I think this challenge was easy and the next time I will start with mobile-first

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

I had some problems with change the color of the list, I dont know how to do that but I will learn in another challenge!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Moses•340
    @mbtenkorang
    Posted over 1 year ago

    Hello 🙋‍♂️ @LucaRiver0n,

    Congratulations on completing this challenge. 👏🎊🥳🎉

    • About styling dots and numbers in front of the list, you'll have to use the ::marker{} tag to target these elements. You may use the following resources to learn more about it
    • 1️⃣CSS Tricks
    • 2️⃣MDN

    I hope this tip helps improve your solution.

    All the best and happy coding 😀🧑‍💻🌟

  • Adann Jacinto•790
    @DanCodeCraft
    Posted over 1 year ago

    Good job overall, @LucaRiver0n!

    To change the color of the list, is this simple:

    li::marker {
      color: your_color_of_choice; -> change the color
      font-size: x.xrem; -> change the size of the marker
    }
    

    I would recommend you pay a bit more attention to the size of fonts, and spacing in general. It will give your pages a whole different look and improvement.

    As well, you should consider using different measuring units, other than px. They do have a purpose and help with accessibility.

    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

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