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

Social Links Profile using Tailwind CSS

tailwind-css
Kyla Marie Angeles•90
@keilalily
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?

This is the first project I’ve completed on Frontend Mentor without using a Figma design file. I’m proud that I was able to recreate the design as closely to the reference as possible, based on my own judgment.

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

The main challenge I encountered was trying to match the design as closely as possible to the reference, since I could only rely on the reference images without knowing the exact font sizes or image dimensions. I overcame this by carefully checking the details and constantly comparing my output with the reference throughout the process.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • VenkataMadhuK•60
    @VenkataMadhuK
    Posted 3 months ago

    You just did great that is some fine work out there well I also done the same thing using tailwindcss so there are so many differences I observed mainly: 1.well in creating buttons I think you have used button tag but I used li tag the difference is not in using html but the way we styled almost tailwind classes look so similar but you create a re-usable button which is I didnot thought about it can also done in that way 2.You used pixel units for width for the picture but I recommend using em and rem units try to look into them if you got time 3.for colors you created your own colors but except green color all colors are available in tailwind css so these are all things I observed in your code please try to give feedback to my code as well

    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