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

Bento Grid with Tailwind

tailwind-css, react
Andrew•420
@timshandrew
A solution to the Bento grid 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?

This was my second project using Tailwind. I gained experience using more of its utility classes, especially those for grid layouts.

If I were to attempt this project again, I would separate the cards into components. Here I decided not to because I saw no way to extract a generalised card component, as none of them share the same structure/styling or state. With this considered, I think it might still be a good idea to separate them in order to make the code more readable.

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

I was trying to set an image larger than its container in order to produce the clipped effect where only a portion of the image is visible. It would not work and I could not figure out why. It turned out to be due to Tailwind's default styling - the 'preflight' which added a max width of 100% to images, thus not letting it exceed the width of its parent.

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

Tailwind and dynamic data

Using Vite, I imported an image from my src/assets folder with 'import imgSrc from ".."'. My understanding is then that imgSrc becomes the resolved path to the image after the build step. Does this just exist as a variable in the scope of the module which imported it then?

The reason I ask this question is that I tried to use a custom Tailwind class of the form bg-[url(imgSrc)]. Tailwind did not produce a class for it during build. As such, I assume it is because the imports act as I have described above?

My prior thought process was that a static resource import was evaluated during the build step and substituted where it was referenced.

Many thanks to anyone who has read this far - this was essentially me thinking aloud and more for documentation of my learning than anything. If anyone has any insight I'd very grateful.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Andrew'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

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.