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

Responsive Article Preview Component w/ Next.js/React/Tailwind

next, react, typescript, tailwind-css
P
Erik S. Carlsten•290
@ecarlste
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 don't think I've ever created an SVG from scratch manually, I'm typically grabbing them from Luide React or something similar.

However for this project I needed to create the toast bubble tail that points downward and I decided to create an SVG from scratch in code to do so. The markdown ended up being pretty straightforward for such a simple SVG, but it was fun to learn the basics nevertheless.

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

When I originally built the desktop/tablet version of the toast share component I used an SVG that was generated in the Figma project to try and get it done quicker. However, I had to display the share links on top of it which ended up making the code pretty ugly and hard to understand.

Eventually I switched to simply using a div for the toast's main bubble and used the custom simple SVG for the toast's tail. This made the code much easier to understand and also made separating the desktop/tablet component from the mobile component much cleaner, since I could simply pass the ShareLinks component to both of them as a child to simplify each of them.

This also meant that I didn't need to absolutely position the links component for the desktop/tablet version since they were now contained with the parent div, which felt much cleaner.

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

I think the biggest thing for me is still wanting to get advice about how to organize the component using semantic HTML.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Erik S. Carlsten's solution.

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.