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

Recipe page

Raphael Siqueira•150
@raphaelsiqueiira
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?

Me orgulho das coisas que aprendi ao fazer essa solução, como o uso de fontes como variáveis no :root, já que até agora eu apenas usava para cores. Também consegui aprender mais sobre pseudo-elementos como o ::marker.

I'm proud of the things I learned while making this solution, like using fonts as variables in :root, since so far I only use it for colors. I also managed to learn more about pseudo-elements like ::marker.

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

Tive dificuldades no começo para estilizar os marcadores das tags e , não havia usado até o momento o pseudo-elemento ::marker, também tive dificuldade com as medidas e senti falta dos arquivos figmas. Mas no fim consegui superar essas dificuldades .

I had difficulties at first when styling the markers for the and tags, I hadn't used the ::marker pseudo-element until then, I also had difficulty with the measurements because I didn't have access to the figmas files. But in the end I managed to overcome these difficulties.

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

Estou aberto a qualquer sugestão

I am open to any suggestions for improvement

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • EFEELE•400
    @EFEELE
    Posted about 1 year ago

    I had a lot of problem with the bottom borders of the table elements, but now looking at your code I see that it is more practical to do it with divs instead of with table.

    Congratulations!!

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