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

Article Preview: ReactJS + TailwindCSS

react, tailwind-css
P
Aero Flamiano•220
@aflamiano-career
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?

I was able to align the callout bubble to the share button.

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

I tried to solve the callout bubble alignment by just putting it in one location but that proved to be too difficult. What I did was to put two instances of the share component on different parent divs.

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

I have 3 areas I which I think need improvement or clarification:

  1. Rounding of the corners of the article along with the image. If I put an overflow-hidden on the parent element, when the share button is clicked on tablet/desktop, the pop-up will also be hidden. My workaround is to reapply the border radius for the children that need it.
  2. Creating the tail of the callout bubble. <div className="w-0 h-0 border-x-10 border-x-transparent border-t-10 border-t-grey900 mx-auto"></div> In my search, this is the cleanest tailwind way I found. However, I don't fully understand it. Can anyone enlighten me?
  3. Having two instances of the Share component. I found it almost impossible to make the share feature be part of the document flow on mobile while also putting it inside the flex item for the share button to capture its center when in tablet/desktop.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • sttilstra•130
    @sttilstra
    Posted 14 days ago

    This looks really good and the responsive layout is great. I see that you used Tailwind. What are some aspects about that framework you like over something like Bootstrap?

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