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

Blog Preview Card with Tailwind CSS

react, tailwind-css, vite, typescript
Nestor Dabon•50
@dabonnestor
A solution to the Blog preview card 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 know I can simply just use plain HTML, CSS, and JavaScript but I couldn't help myself using Vite as my main development build tool for simple projects.

I also use React because I've been using it for several years on different projects and I love writing code in JSX.

Of course, Tailwind CSS is the highlight of this project. I'm so happy that Tailwind CSS has improved a lot over the years by adding support to the CSS grid and more.

I commend the Figma design. It's a well-thought design which makes it easier for me to work with spacings, sizes, etc.

Overall, the total DX is great and I'm proud of it. Cheers! 🎉

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

I'm trying to make a general rule of thumb for myself to deal with CSS layouts.

  • Grid = Layout
  • Flexbox = Component

So trying to be a hotshot, it was a challenge for me to recall how to use a CSS grid just to center a component (blog preview card). After a little research, I managed to resolve my problem. I highly recommend to use this tool to visualize your CSS grid here

Then for the card component, I use Flexbox which I overly use for everything.

Support for CSS grid in Tailwind CSS is fairly limited but it has the common usage for the grid. One thing I like about Tailwind CSS is that you can write custom CSS that is not supported with Tailwind CSS utilities.

You can read more information on the docs here

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

Please feel free to ask me some questions or give me some feedback. Cheers! 🍻

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mayank Kushwah•80
    @mynkRog
    Posted 11 months ago

    👍🏻

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