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

Mobile-first design with Tailwind CSS

tailwind-css
P
KoalaChang•110
@KoalaChang
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 use Tailwind CSS in this project for the first time, though I'm still not familiar with the workflow and the way to use it, I can tell that it would be easier to build consistent styles and layouts with Tailwind.

I would like to combine Tailwind and React, and see how components can work efficiently with these two frameworks.

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

The transformation from original CSS properties to Tailwind CSS needs some time to get familiar with.

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

I would like to know the workflow of Tailwind with React, how do people start the project? Do they start with the html tags and then separate it into different components, or just simply start from the top of the webpage and make the components once encounter them?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Esteban•670
    @evertzner
    Posted 9 months ago

    Hi, nice job!

    What i do with tailwind/react projects is that first i create the components that I know I will use, let's say Main.tsx, Card.tsx and Button.tsx. Then inside each component I write the html and dummy content that I need (for example, using Lorem Ipsum text). Then after having all the content I need, I start with the tailwind implementation. Most of the times, I go from general to specific, in this case I do first Main then Card and last Button. After finish this or in the meantime I also take a look if there is something that can be converted into another component. For example, let's say that inside Card I have a list of items, well in that case I move out the list and create a component call Items.

    Hope it helps somehow

    Marked as helpful

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