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

Social Links Profile Using Flexbox

Linda Jensen•80
@lindajensen
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 the fact that I figured out the whole link-button-hove situation. I thought the links where suppose to be buttons (maybe they were?) but then I couldn't get the hover thing to work. So then I tried wrapping the buttons in anchor-tags which solved the problem but when I tried to validate my code I got a bunch of errors. But eventually I figured out that they were suppose to be links (duh it's called social links profile lol).

What would I do differently? I don't know. Maybe try and finish the challenge in one sitting, because it's difficult working on it and then not doing anythin on it for like a day and then picking it up again. But I have a full-time job and work has been crazy for a few days and sleep is a thing so...

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

The button-problem. Which wasn't really a problem because they were suppose to be links. I'm guessing. I also had a problem with the bottom part of my buttons (before I turned them into links) disappering which I have no idea what that was about or how I solved it.

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

When are you suppose to use buttons and when are you suppose to use links? I mean links are links and buttons are buttons, but I mean what do you use buttons for? Is it just like submit, send, and stuff like that?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • SIBI•80
    @sibi404
    Posted about 1 year ago

    You have to use links to take the user to a new location. It can be different page or different section of the current page. Buttons are used to trigger any actions like submitting forms, opening menu etc.

    Your solution is very good and I appreciate your work

  • Bojan Lukic•260
    @bojanognjen
    Posted about 1 year ago

    It looks good. I think only you should add padding on main holder to 40 pixels from right and left side.

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.

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