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

Social links profile using Tailwind CSS

tailwind-css
ehennes•70
@ehennes
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What did you find difficult while building the project?

  • It was my first time using Tailwind CSS. There was definitely a learning curve with the syntax, and I found there to be a lot of nuance when you wanted to customize the base styling (extending vs overwriting the theme, updating config file vs updating input css manually, updating config file vs creating a one-off class, etc.). Because of this, the build was pretty slow for such a straightforward project, but I think if I were to use it again it would be much faster.

Which areas of your code are you unsure of?

  • Mostly my implementation of Tailwind. It definitely bulked up my index.html file a lot with classes, but I was not sure if there are best practices around the order of the classes on elements and if there are any best practices re: the config file that I failed to implement.

Do you have any questions about best practices?

  • For Tailwind - see previous answer, as well as:
  1. I added the Tailwind build process to my npm dev script - I was unsure if this was a good way to go about this / if there are better ways.
  • For Frontend Mentor workflow:
  1. Are there any files from the starter that I should have kept in my final project, or any others that should be removed?
  2. Are there best practices on file structure for smaller projects like this one that I have not implemented?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on ehennes'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.