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

social links card with simple hover effects

vicky2805vky•70
@vicky2805vky
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?

this is my first project which I only created using an image not figma.

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

as I use image I have some problems in finding pixel measurements I think my website is almost similar to the design but it is so small.

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

someone please tell me how do you deal with this measurement problem. as you can see my website look similar but it is small

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • keltiek•210
    @keltiek
    Posted about 1 year ago

    I'm not sure if it will help you, but I'm using "Pixel Perfect Pro" extension on Chrome, and it makes it easier to follow the design without figma.

  • Ken•310
    @kenwhatts
    Posted over 1 year ago

    Great

    I just have some suggestion:

    1. Instead of using fixed width & height like px, try using a more fluid size like percentage %
    2. Don't use H2 without using H1 first. They should be in order like:
    <h1>
    <h2>
    <h3>
    <!--etc-->
    

    and take note, dont simply use headings just to make a text smaller or bigger than the other because they are suppose to give meaning to a content. You can instead use <div> or <p> and just add a style.

    Also its great you used list for listing links

  • ELMudyr•240
    @ELMudyr
    Posted over 1 year ago

    Great work you nailed it, I would be interested if you found a way to find a the resolution from an image.

  • Moniruzzaman Monir•760
    @ad-monir2001
    Posted over 1 year ago

    Hey there, You have done a nice project. Keep coding. I wish a better future of you of 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

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