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

Tailwind, responsive design using tailwind

tailwind-css
Bilesanmi Ahmad•20
@bilesanmiahmad
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sultan Farrel•110
    @SultanFarrel
    Posted 11 months ago

    First of all, great job on completing the challenge! It takes a lot of dedication to build a web page from scratch, and you've done really well. The overall structure looks solid, and I especially liked how you've made use of Tailwind CSS for styling. The layout is clean, and the use of fonts and spacing gives it a polished look.

    That being said, I have a few suggestions that could help push the project even closer to the original design:

    • Image Responsiveness: While the omelette image looks great, it could benefit from being fully responsive. Right now, the height is fixed at h-80, which may not adapt well to different screen sizes. Using responsive height utilities like h-auto or experimenting with aspect ratio utilities could make the image more adaptable across devices.

    • Typography: I noticed the font sizes and weights are a bit off compared to the original design. You can fine-tune these by checking the exact sizes and weights used in the design and applying them consistently. For example, the recipe title could be larger or more prominent to better capture attention.

    • Spacing & Alignment: Some sections (like the headers and paragraphs) could use a bit more breathing room. Pay attention to the margins and padding around text elements. Tailwind offers excellent tools like space-y, mt, and mb to help with that.

    • Color Adjustments: The pink background in the preparation time section is a nice touch, but it feels slightly different from the intended design. You might want to tweak the color or its intensity to match the exact tones in the original design. Similarly, adjusting the shades of gray used in the nutrition table could bring it closer to the expected result.

    • Accessibility: Lastly, considering adding alt text for the image and making sure the contrast ratios for text against background colors meet accessibility standards. This is a small change that can make a big difference, especially for users with visual impairments.

    All in all, you're on the right track! With a few tweaks here and there, you’ll get even closer to the final design. Keep up the great work – I’m excited to see how you continue improving this project!

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