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

Responsive recipe page using tailwindcss

tailwind-css
P
NunoJDMachado•150
@NunoJDMachado
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 learning about tailwind custom color classes like text-[<hexcode>]. But maybe next time I'll create css classes so the code is a bit cleaner.

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

1 - Struggled with managing the font colour and weight differences in the "Preperation time" card and the "Instructions" section, but after some experimentation it turned out alright.

2 - Also struggled with the table alignment to get it looking as close to the design as possible. A mixture of width and padding classes on the <td> elements seems to have done the trick.

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

I would like some feedback on points 1 and 2 above. Although I managed something I'm not sure if there is a better approach.

Also some feedback about the semantic tags would be helpful. I seem to be abusing <section> a lot. I thought about <article>, but these aren't really articles? dunno

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    BlonoBuccellati•330
    @BlonoBuccellati
    Posted 3 months ago

    Great work! As for point 2, Sorry, I'm not sure what the best practice is either.But I had a couple of thoughts:

    • font-[700] corresponds to font-bold, and font-[600] to font-semibold. Both are utility classes provided by default in Tailwind CSS.
      So for better readability and maintainability, using font-bold or font-semibold where possible might be preferable.

    • The <hr> element is typically used to indicate a thematic break in content. However, if you're already using <section> elements to define content structure, <hr> might be unnecessary.
      In such cases, it may be more appropriate to handle visual separation with CSS instead.

    just hoping it might be helpful!

    Marked as helpful
  • Nguyễn Thanh Sang•60
    @Lux0702
    Posted 4 months ago

    Good Job !

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub