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

Responsive solution using Tailwind CSS

tailwind-css, vite
Abhishek Kumar•100
@abhixdev
A solution to the Social links profile 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've made the design 90% accurate, but the size of the bio text is the same as that of the button, which is not accurate. In the design, the button is larger than the bio text. I could have created this without using Flexbox, but I thought since all items are in columns, flex is necessary. Perhaps another approach could have been better. This was my best attempt.

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

Font Sizes and font weights. I guessed the font weights but can't figure out font sizes.

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

I'm happy to help with any queries.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 1 year ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have a suggestion regarding your code that I believe will be of great interest to you.

    MAKING ACCESSIBLE LINKS:

    • The links like Github, Frontend Mentor are needed to be actual <a> elements which are wrapped up using li and ul elements. The button element is not appropriate to use in this solution. because button element can't be used for navigation purposes that's why we want to use a elements.

    • This is the current markup,
    <button class="...">GitHub</button>
    <button class="...">Frontend Mentor</button>
      ....
    

    • In order to make this solution accessible, we need to use <a> elements with href attribute. Here's the example
    <ul>
        <li>
           <a href="#" class="...">Github</a>
        </li>
        <li>
           <a href="#" class="...">Frontend Mentor</a>
         </li>
        ...
    </ul>
    ....
    

    • Additionally, After converting button into a elements you need to add block tailwind class for a so that you it look like button. because by default a elements are inline so that we are changing it into block level elements.

    • If you have any questions or need further clarification feel free to reach out to me.

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    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