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

Solution Article preview component

tailwind-css
Stefan Bojkovski•720
@xStephx
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Igor•290
    @whiteriver-dev
    Posted 8 months ago

    Hi Stef! You are one of the people I look to when I try to explore how other people have approached certain problems, and while I was looking through this project of yours - I was impressed with how you created it.

    One thing that I came across though - not sure if you have noticed - is that if you test it on a small phone screen size (320px) your Share button overlaps and covers a portion of the Social Media icons. Just wanted to let you know.

    Besides that, keep up the great work - and know that I often look up to your work as a good example.

    Marked as helpful
  • OmarKhaled-5758•180
    @omarkhaled-code
    Posted 11 months ago

    The implementation is very excellent, but I have a small addition, which is to make a small animation when the sharing bar appears.

    Marked as helpful
  • Neto•210
    @denetodev
    Posted 12 months ago

    "Your work looks fantastic. I reviewed your code to understand how you arrived at this solution, and I was impressed by how efficiently you achieved the result with such concise code. It’s both simple and effective. Well done!"

  • KamronbekBotirjonov•240
    @KamronbekBotirjonov
    Posted about 1 year ago

    Steph, can you give me your phone number?

  • qvazi•100
    @qvazi
    Posted about 1 year ago

    What do you think about using ::after for share-btn-content to make share-arrow.

  • Abdullah ElMetwali•190
    @abdullahelmetwali
    Posted about 1 year ago

    Well done but what do u think about using flexbox instead of absolute , make code more easier & flexible

  • Rupak Mukherjee•1,370
    @hannibal1631
    Posted about 1 year ago

    Great Job buddy!! Looks and works well.

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

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

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

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