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

Tailwind / React

react, tailwind-css
Mark Angel Papio•810
@ExiviuZ
A solution to the Social links profile 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

  • Ehsan Tatasadi•1,800
    @tatasadi
    Posted over 1 year ago

    Hey there,

    Great job on completing this challenge! Here are some suggestions to further enhance your project:

    Use Main Element for Main Content

    Consider wrapping your main content in a <main> element instead of a <div>. This semantic HTML element helps with accessibility and clearly defines the primary content of your webpage.

    Reevaluate Width Property

    The w-[90%] style makes your app responsive, but you might want to consider if a max-width of 350px and a padding is sufficient for all devices.

    Use REM Units Consistently

    Switching from pixels to REM units for padding, margins, font sizes, etc., can improve accessibility and maintain consistency across different screen sizes. REM units are based on the root font size, making it easier to scale your design.

    Tailwind's Predefined Classes

    Tailwind offers a wide range of predefined padding, margin, font size, and other utility classes. For example, p-4 translates to padding: 1rem; if the base font size is 16px. Using these predefined classes can simplify your code and make it more readable. Check the Tailwind documentation for a full list of available classes.

    Simplify Social Links Styling

    Instead of repeating styles for each social link, you can create a mutual class and apply the same set of Tailwind utilities to that class in your css file. This approach DRYs up your code and makes it easier to maintain.

    Example Refinement:

    <div className="flex flex-col gap-4">
      <div className="social-link">Github</div>
      <div className="social-link">Frontend Mentor</div>
      <div className="social-link">LinkedIn</div>
      <div className="social-link">Twitter</div>
      <div className="social-link">Instagram</div>
    </div>
    
    .social-link {
       bg-neutral-app-grey font-medium rounded-[0.625rem] py-3 px-4 hover:bg-primary-app-green hover:transition-colors hover:text-neutral-app-off-black cursor-pointer
    }
    

    Implementing these suggestions will not only improve your code's efficiency and readability but also enhance the overall user experience. Keep up the excellent 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