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

Frontend Mentor | Recipe page with HTML and CSS

sass/scss, bem
P
Matthef•190
@MatFrat95
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?

The part im proud of the most is for sure reusable classes i created for this project. Besides that I finaly could try to make table for the first time, i search here and on MDN site and found solutions to problems that apears one after another.

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

The most challenging part for me was - as i mentioned earlier, creating table. Another issue i had with this project was settings on list item marker. It was very difficult to me to make it look like on preview.

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

I'd like to know few things. Would it be better to use sections for every single part of recepie page, or just use divs with classes as i did in project. I need deeper understanding of list and table creating, will for sure search for more information about it. I wanna know how to set marker on list to make dot centered verticaly regard to number of lines like on project - thats the only thing i could't find anywhere.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohammed-Abol-Fotouh•80
    @Mohammed-Abol-Fotouh
    Posted 8 months ago

    great 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