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

Recipe Page - Responsive Design with Tailwind CSS

tailwind-css
antonioReynaldo•80
@antonioReynaldo
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?

I’m proud of how clean and responsive the design turned out using only Tailwind CSS. The page maintains a consistent look and feel across all devices. Next time, I would explore adding interactive elements, such as an ingredients checklist or animated transitions, to enhance user engagement.

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

One challenge was ensuring that the layout remained consistent across screen sizes without overcrowding the content. I solved this by using Tailwind’s responsive utilities and testing extensively on different devices. Another challenge was balancing white space and content density for readability, which I refined using Tailwind’s spacing and typography classes.

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

I would love feedback on improving the accessibility of the page, especially for users navigating with screen readers. Additionally, suggestions on how to further optimize loading times, especially for images, would be helpful.

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 antonioReynaldo'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
Frontend Mentor logo

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 1st-party linked stylesheets, and styles within <style> tags.

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.