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

Social Links Profile Solution

P
Jeff Guleserian•500
@jguleserian
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?

Greetings, Everyone:

I had a lot of fun doing this project; it seems like it could be functional piece to utilize on a number of ways either on a site, or on social media.

What I was most proud of was the length of time it took me to complete to complete the project. It seems like with each project, it goes a little faster. I also incorporated some suggestions graciously given to me by @JEWebDev from my last project. I always appreciate it when someone takes a look and give encouragement, or better yet, pointers on how to do better.

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

While I didn't have issues with the stated challenges, I really wanted to become more creative with the links themselves. So, not only did I make them live links to the respective site figured on the link button, but I also added the hover states (required in the project) and an active state for those using a mouse. What I really wanted to do was to create a "visited" state for the button itself, but I couldn't seem to get it to work using pseudo-classes. I tried several combinations of selectors, but never was successful.

I feel like I could do it with JavaScript, but then, since nothing else needed JS, it would have been a lot of extra work for very little gain. If someone knows how to do it using only CSS and HTML, I would love to know.

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

(See previous section)

Thank you for taking a look at my solution. If you have any helpful suggestions, I would be grateful.

Happy coding!

Jeff

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • naufaluqh•90
    @naufaluqh
    Posted 11 months ago

    good job mate

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