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

Blog Preview Card

tailwind-css, vite
P
Darkstar•1,380
@DarkstarXDD
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?

Built with. 🔨

  • HTML.
  • Tailwind.
  • Vite.

Features. ✨

  • The requirements of the project stated that the font sizes need to slightly change with the screen size, but without using media queries. So I used the clamp() function on the font size.
    .text-clamp-100 {
      font-size: clamp(0.75rem, 2vw, 0.875rem);
    }
    
  • To make the whole card clickable, I used a pseudo element. I added the pseudo element to the a inside the h2. Then made the card component position: relative. Now when top-0 right-0 bottom-0 left-0 is given to the pseudo element, it will be same size as the card component.
  • Added the hover effect to the card component. So when hovered over the card the box-shadow will get slightly bigger.

New Things Learned. 🎓

  • It's my first time using Tailwind, so had to learn how to setup a project with it.
  • Using the the Tailwind CSS IntelliSense VS Code plugin. It was super helpful since it shows the underlying CSS properties for each utility class.
  • How to use the tailwind.config.js file to extend the default theme to include my own custom values.
  • Using @layer to include my own classes.
  • When using pseudo elements, Tailwind will automatically add content: '' by default so you don’t have to specify it unless you want a different value.
What specific areas of your project would you like help with?

Would love some overall feedback on any areas where I can improve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Zahid Shaikh•80
    @The-Lone-Druid
    Posted 7 months ago

    Great work my friend 🥂

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