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

Responsive Social Media landing page using TailwindCSS

tailwind-css
Julian Jones•80
@JulianJ96
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'm most proud of completing the project because, without the figma files giving the specific measurements, I had to eyeball the length and width of the card and buttons so that took me quite a while to figure out. What I would do differently, is make sure that I have the pro version of frontend mentor so that I can have a bit of more professional workflow.

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

I don't know if it was my eyes, but I couldn't figure out how to get the "London, united kingdom" part directly underneath the title, so I took off the top and bottom margins hoping that it did something. Also, the colors that were given in the styles guide at leas to me looked off from the finished image that was provided but I still went with it.

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

I mentioned earlier that I wasn't able to get the "London, United Kingdom" part directly underneath the title so I was wondering what should I do differently there, other than that; I think I did ok with the project.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chris Ebube Roland•160
    @ChrisRoland
    Posted 8 months ago

    Nice work!

    To solve the issue you mentioned. It should be pretty easy since you're using Tailwind, you could simply add text-center to the wrapping container or directly to the h2 element containing the text.

    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