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

Recipe Page using HTML and CSS

Kauê Alves Vecchia•90
@kauevecchia
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?

Honestly, i'm not very proud of my result in the challenge, because there were things i didn't know how to do and i had to do some research, causing some parts of my code not to be written by me. But at least i was able to notice things that i have to study more.

Sinceramente, não estou muito orgulhoso do meu resultado no desafio, porque havia coisas que não sabia fazer e tive que fazer algumas pesquisas, fazendo com que algumas partes do meu código não fossem escritas por mim. Mas pelo menos consegui notar coisas que tenho que estudar mais.

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

there were some things I couldn't replicate from the design, so I had to search for solutions, so some parts of my code are the solutions from my search.

tinha algumas coisas que eu não conseguia replicar do design, então tive que pesquisar por soluções, então algumas partes do meu código são as soluções da minha pesquisa

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

I think that the problems and doubts I had in this challenge, I was able to find the answers through my research.

acho que os problemas e as dúvidas que eu tive nesse desafio, eu consegui achar as respostas através das minhas pesquisas

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kauê Alves Vecchia's solution.

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.