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

social-links-profile with custom css

Tanadol Moungmontree•40
@tanadolMo
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Weberowsky•130
    @Weberowsky
    Posted 4 months ago

    Your social profile card is nearly identical to the design – great work overall! Here are a few detailed suggestions to polish it even further:

    • Viewport Overflow: The site currently overflows the viewport. This might be due to the use of width: 100dvw; and height: 100dvh; on the HTML and body. These units can sometimes lead to unexpected behavior with scrollbars. Consider using 100vw/100vh or adjusting the layout so that the content naturally fits within the viewport without causing overflow.

    • Missing Hover Effects: The buttons lack the hover effects as shown in the design files (active-states.jpg). Adding CSS hover states will enhance interactivity and better align the final product with the provided design specifications.

    • CSS Organization: While embedding CSS within the HTML file is acceptable for small projects, moving your CSS to an external stylesheet is a best practice. This not only improves maintainability and readability but also allows for easier reuse of styles in larger projects.

    Keep refining these details, and your project will be even more polished and professional. Great job, and keep up the excellent work!

    Marked as helpful
  • Lưu Khang Huy•30
    @huy293
    Posted 4 months ago

    drf

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