Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 23 days ago

HTML Tailwind CSS (via CDN) Plain CSS (for custom box-shadow)

fatihaosman•40
@fatihaosman
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'm most proud of how the custom box shadow turned out — it adds a nice layered, standout effect to the card and gives it personality. It was a small detail, but it made a big visual difference.

Next time, I’d try to fully implement it using Tailwind’s utility classes instead of inline styles. That way, the styling would be more consistent and easier to manage within the Tailwind framework.

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

Overall, the project was quite straightforward. The only minor challenge I faced was getting the box shadow to look exactly how I envisioned it. Tailwind’s default shadows didn’t give me the bold effect I was going for, so I ended up customizing it with inline styles to get the precise look.

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

I’d really appreciate help with implementing the box shadow using Tailwind’s utility classes instead of custom inline styles. I wasn’t sure how to achieve the bold shadow effect I wanted using only Tailwind, so I resorted to writing a custom box-shadow in the style attribute.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yousef Adel•70
    @YousefAdelGit
    Posted 23 days ago

    very good but kind of small

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub