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

Blog Preview Card with tailwindcss and @font-face

tailwind-css, node
P
Stefan Vetsch•140
@vstm
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?

This time I used prettier with the tailwind plugin to format the code, so all the tailwind classes are sorted properly.

Also I used the screenshots from the design to implement it first, it was quite cumbersome to get all the measurements (font-sizes, heights and colors) because the image was antialiased. Then I used the figma to correct the initial values.

Also I was distracting myself during this challenge by watching youtoube videos, I should stop that :D

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

Somehow the Figma download did not work so I used the screenshots to start the challenge but it was very cumbersome. Finally I got the Figma download to work by copying the URL and use wget from another host.

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

Any feedback on tailwind specific issues are appreciated, other feedback is appreciated as well.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi!

    That's a good catch with ul tag (html tag) with "Learning" tag (actual tag)! I thought that there could be several of them, but it just doesn't strike me to use list tags =)

    I guess you missed a hover effect a bit =) The header should be yellow under the hover and it should have cursor: pointer. And you can add transition effect to make hover smoother. Also I suppose since it's clickable elements there should be a link inside it.

    P.S If it was a youtube videos explaining advanced css topics than that's ok, if it was cats riding vacuum bots than maybe no, but if it was cats explaining advanced css topics while riding vacuum bots than I confused and want to see it.

    Marked as helpful

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