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

Article preview component

tailwind-css
Larisa•130
@LarisaKampe
A solution to the Article preview component 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?

Using a combination of tailwind and JS :)

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

I need a bit of help with share button in mobile preview. Since it is toggle on/off in mobile screen size it is positioned below the 'share-box' but when I set position and put the z-1 it is on top but on same position (because of flex I believe) so one of the link is below it and it is not usable 😅.

And if anyone knows a good JS course? I watched a few and when I do watch and follow along it is very logical and easy but this little bit of code took me long enough to understand that I need to really master the basics and learn to recognize the steps myself.

Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • didgiman•130
    @didgiman
    Posted 7 months ago

    A simple solution for your problem with the button is to include another share button in the share popup section. You need to anyway, because it should have a different color than the other one.

    A few issues I see with your solution:

    • The location of the share button
    • The appearance of the share popup on mobile. It should span the complete with of the component
    • On desktop, I'm missing the triangle shape beneath the share popup to make it look like a text balloon

    All in all not a bad attempt, with some minor adjustments to make it great. Nice work.

    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 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