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

responsive recipe

Merouanos•140
@Merouanos
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?

just aligments

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

trying to copy the exact widths and heights of the design

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • qutubahmed732•120
    @qutubahmed732
    Posted 9 months ago

    Hey everyone! Just wanted to share a little review on the recipe page I created. I focused on keeping the layout clean and user-friendly, making it easy to follow the steps. Here’s a quick overview:

    Presentation: I organized the ingredients and instructions separately, so it’s simple for users to read through each section without getting overwhelmed. I might add a few icons or images alongside each step to make it feel even more engaging and visually interesting.

    Readability: I chose a clear font for easy reading, but I’m thinking about bumping up the font size for the instructions a little to make it even easier on the eyes.

    Images: I added some delicious-looking food photo to keep the page lively. I’m considering adding a subtle hover effect on the images for a touch of interactivity.

    Personal Touch: I’m thinking about adding a short intro for each recipe—maybe a fun fact or a little story about why I love it. I feel like this would make the page feel more personal and relatable.

    Mobile View: I’ve tested it on mobile, but I’d love some feedback on how it looks on smaller screens. I want it to be just as functional on phones since many people use their devices while cooking!

    I’d love any feedback or suggestions to make it even better. Thanks for taking a look! 😊

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