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

Responsive Social links profile | Vanilla JS

Renita M•40
@renitam
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?

Built with semantic HTML, custom CSS, and Vanilla JavaScript to meet the challenge specs. No frameworks—just clean, lightweight code. Deployed via GitHub Pages for quick and easy access. Focused on responsive design and functionality using native JavaScript.

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

I had some trouble with my @media css statements. I forgot they go after the original css, not before. Also, I was trying to implement color variables for easier coding and realized too late into the challenge that I had to store variables under :root {}, so there was some repetition there.

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

I wanted to make the cursor match the Figma without substituting it for an image file, because I feel like that's doing a lot. Any suggestions?

Update

I went ahead and used the cursor: url(), pointer property, but there's some lag in how it renders. As if the cursor is glitching from one spot to another upon hover. Any advice on how to fix?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muskan Fatima•160
    @muskan-fatim
    Posted 2 months ago

    Hey! Awesome job on your solution! 👏

    I noticed you mentioned wanting to make the cursor match your Figma design without using an image file (which I agree is a great idea to keep things clean and lightweight).

    Here’s a suggestion you might find helpful:

    Instead of using an image, you can create a custom cursor using just HTML, CSS, and JavaScript. For example:

    <!-- HTML -->
    <div id="custom-cursor"></div>
    
    /* CSS */
    #custom-cursor {
      position: fixed;
      width: 20px;
      height: 20px;
      border: 2px solid #000; /* Adjust to match your Figma design */
      border-radius: 50%; /* You can customize this with clip-path for unique shapes */
      pointer-events: none;
      z-index: 9999;
      transition: transform 0.1s ease;
    }
    
    // JavaScript
    const cursor = document.getElementById('custom-cursor');
    document.addEventListener('mousemove', (e) => {
      cursor.style.left = `${e.clientX}px`;
      cursor.style.top = `${e.clientY}px`;
    });
    

    This lets you style your cursor however you want without needing to import any image files. You can even add hover effects or animations if you like. Let me know if you’d like help customizing it to match your Figma style exactly!

    Keep up the great work 💻✨


    Marked as helpful
  • Renita M•40
    @renitam
    Posted about 2 months ago

    Thank you, Muskan! I ended up opting for the svg url() option, but I love the attention to detail. I'm wondering how I'd go about calculating the performance difference between solutions. Happy Coding!

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