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

My solution of Recipe page FrontendMentor Challengue

jorge arevalo•50
@JDev-8
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?

This project has represented a significant challenge in my path as a frontend developer, possibly the most demanding to date. Confronting the specific HTML structure proposed by Frontend Mentor forced me to delve deeper into the use of CSS selectors, exploring various strategies to achieve the desired results. The need to adapt the design to a predefined structure was a stimulating challenge. Through this process, I consolidated my understanding of class selectors, IDs, attributes, and pseudo-classes, learning how to combine them effectively to target specific elements and apply precise styles to them.

With each challenge, I feel more confident and prepared to take on more complex projects. My journey in the world of frontend continues, and I am eager to continue learning and growing as a developer.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mr Rainman•130
    @phantomgizmo
    Posted 7 months ago

    The website looks good!

    Maybe it could be improved by making the image more responsive by setting the width with max-width (or max-inline-size) of 100% instead of static width.

    Also the main container (or wrapper) seems to has a min-width on a larger screen. Maybe it could be improved by removing that so it can resize smoothly when user change browser width. My guess is you set min-width so the image won't overflow, so yeah i guess that's still okay.

    Overall, 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