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

Social links profile using HTML and CSS

Samuel Adeola Orogun•80
@samadeola1
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 think i did well, thinking the width might be too much tho

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

Nothing much, really, getting the hang of it

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

Anything the community feels needs to be corrected

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdiaziz•170
    @0paziz
    Posted 4 months ago

    hey, nice job but one thing i have noticed its that you have assign the width with invalid value (width: 60vh;) the vh unit is based on the height of the viewport, so it controls vertical dimensions. If you meant to set the width relative to height for a specific effect, you might need to use CSS grid, flexbox, or aspect-ratio to maintain proportions.

    have a nice day.

    Marked as helpful
  • P
    Jayco•470
    @jayco01
    Posted 4 months ago

    Hey Samuel! Great job on your solution! I like how you used :root for color variables. It's a nice way to keep things organized. I've never seen that before, might have to give it a try next time.

    A couple of suggestions:

    • Try using CSS classes instead of styling generic elements (h1, p, button) to make your HTML cleaner and more reusable.

    • The buttons are a bit too wide; adjusting the width or adding max-width might make them look better.

    • Since these are social media links, using <a> tags instead of <button> would be more semantic and functional.

    Overall, solid work! Keep it up!

    Marked as helpful
  • P
    toshirokubota•1,320
    @toshirokubota
    Posted 4 months ago

    Hi, your solution looks very good. One comment I can add is that you do not have :focus on button elements. I would add the pseudo class with button:hover. This way, the user can get a feedback from tab based selection of buttons.

    Happy coding!

    Marked as helpful

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