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

Social-link profile using JavaScript, HTML, and CSS

Kyle Netterville•20
@dkdkdkd222
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 very proud to say that I am getting better at HTML and CSS, and I'm excited to say that I have learned more about the transition effect in CSS.

I am applying links for the first time using JS, which has allowed me to understand how the methods work better.

What I would do differently next time is start to try React and see how it goes.

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

The biggest challenge that I encountered was the picture. Although the funny part of why nothing was being applied to the image, was because I didn't have a class enabled to it. LOL.

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

Specific areas of my project that I would like help with is just tips on what I should know about JavaScript, and how it can be used even more when it comes to web development.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted 11 months ago

    Hey there!

    Cool work, it's very interesting way to make links. I've never heard about windows.location before =)

    If you don't mind, there is a couple of suggestions.

    • Semantically correct to use a tags instead of buttons here.
    • Also, since it's a list, it's better to use ul tag here with li inside.
    • main very important semantic tag and every page should contain it.
    • And you can reduce number of tags - for example, there is no need in picture here - you can style img directly. That could be said about span wrapper for the links.

    And a couple things about css.

    • You can get rid of border: none of the container - it's a default value, so there is no need to specify it.
    • There is a bit overkill with margins =) Try to remove margin-top: 100px; of the name element and margin-bottom: -88px; of the picture and you'll see that everything align just right =)
    • It's better to use rem for font sizes. It's a special values which depend on th browser font settings.

    It's totally ok, if you just want to practice something unusual, so, please take my words as hints to best practices, not criticism =)

    Oh, and about JS and web pages there are plenty of possibilities =) Almost every interactive element made with JS. Like sliders, thicker, accordions and stuff. You can even make a simple game with JS right on the web page =)

    So, congrats with completing challenge, you use creative approach, so keep going =)

  • Affan Amer•350
    @AffanRM
    Posted 11 months ago

    Awesome work on the website! I like your unique touch about adding different background colors for different buttons. Regarding your question about Javascript, one creative and nice way I found in this project to implement JavaScript is by creating a light theme as well, and then the user can toggle between the light and dark themes. This is a simple task, but it helps get better at understanding the basic implementation of JavaScript, and it also looks really cool! I did the same for my project, and if you need any further help with how to achieve this, let me know!

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub