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

Blog preview card using tailwindcss, next.js, flexbox

next, tailwind-css, react
P
BlonoBuccellati•320
@BlonoBuccellati
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 take pride in the fact that I've gotten used to UI development in just a few days. This time, I introduced "prettier-plugin-tailwindcss." Next time, I want to customize the elements listed in the design system to make them more suitable.

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

The first challenge was with the Image tag from Next.js's next/image. Since the height and width were automatically adjusted, I had to set fill, but controlling its behavior was quite difficult. I found a YouTube video explaining how to use it, which helped me resolve the issue.

The second challenge was customizing Tailwind CSS. I solved this by reading several articles and the Tailwind documentation. However, I realized that my knowledge is still far from sufficient.

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

Since my knowledge of React, Next.js, and Tailwind is still shallow, I appreciate any kind of feedback.

What I’m particularly concerned about is how much and how to customize the design system. I understand that in the Utility-First approach, premature abstraction should be avoided, but I’m not sure how to strike the right balance. If you have any insights, I would greatly appreciate it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ∀lex•70
    @Vlekzander
    Posted 4 months ago

    Great project, you're really close!

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