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

Responsive blog priview card using tailwind

tailwind-css
Dheerendra Kumar•90
@acekant
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?

Hello friends,

I’m Dheerendra Kumar, and I’m excited to share my journey of completing this challenge. A few days ago, I watched a Tailwind CSS course, and just before that, I had learned CSS. Instead of working with plain CSS, I decided to jump straight into Tailwind CSS (v3) and build this challenge using it. I am most proud of in compelete this challenge using Tailwind,

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

What I Learned Through this project, I explored how to add custom CSS and create custom utilities like spacing, colors, margins, and padding. I also gained a deeper understanding of Tailwind’s unique approach—such as using hidden instead of display: none, since Tailwind doesn’t include display: none by default. These small differences helped me understand Tailwind’s philosophy better and improved my workflow.

Where I Needed Support To overcome challenges, I turned to ChatGPT for help. It guided me in:

Implementing custom properties and utilities in Tailwind CSS Exporting all Tailwind styles into a style.css file using DevTools Applying rounded borders correctly, [me: I give my written retrospective to Chatgpt for making it grammar correct and engaging] This challenge was a great learning experience, and I look forward to refining my skills further! 🚀

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

I would like to help how to make CSS utilities so that your work done faster, responsive layout design(grid and flexbox) etc. thank you reading till here

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • jomojas•80
    @jomojas
    Posted 24 days ago

    #Greeting! I am glad to have this opportunity to post feedback on your solution. Really good job of your solution. I am also a newbie on frontend. Let's move on together. #Feedback I personally don't want to criticize on your solution, since it's already a good job. But to keep this community open and prosperous, and improve together, I am glad to come up with my views. I have visited your code, and I found you use div tag on many text elements. Personally speaking, I think using p tag for text elements is a good practice and div tags are mostly used to surround other elements. That's just my opinion. Let's move on and improve our skills.

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