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

Social links Challenge | WarmColor/Shadows/SimpleAnimation | HTML5/CSS

accessibility, animation
zh4r•150
@zh4r
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?

Did much faster than previous challenge, while still adding more styles.

I love the look and feel of the final product.

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

Couldn't figure out how to make the footer stick to the bottom while not in collision with other elements, and hide when it collides with the content above it.

Any ideas are welcome ^^

Overlooked some paddings and margins.

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

I would love for someone to give me a Meta tags/Accessibility review!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted over 1 year ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have a suggestion regarding your code that I believe will be of great interest to you.

    CSS 🎨:

    • Let me explain, How you can easily center the component for better layout without usage of absolute positioning.

    • We don't need to use absolute to center the component both horizontally & vertically. Because using absolute will not dynamical centers our component at all states

    • Using this method with also causes in cutting-off your component on mobile devices during their landscape mode.

    • To properly center the component in the page, you should use Flexbox or Grid layout. You can read more about centering in CSS here 📚.

    • For this demonstration we use css Grid to center the component
    body {
        min-height: 100vh;
        display: grid;
        place-items: center;
    }
    
    • Now remove these styles, after removing you can able to see the changes
    main {
      position: absolute;
      top: 50%;
      transform: translate(0, -50%);
    }
    

    • Now your component has been properly centered.

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • P
    Daniel 🛸•44,830
    @danielmrz-dev
    Posted over 1 year ago

    Hello there!

    Congrats on completing the challenge! ✅

    Your solution looks great!

    📌 It's recommended to use semantic HTML elements like <ul> and <li> for creating lists. This ensures that your code is more accessible, maintainable, and semantically meaningful.

    Here's and example on how you can refactor your code:

    After Refactoring

    <ul class="list-container">
        <li><a href="#">Github</a></li>
        <li><a href="#">Frontend Mentor</a></li>
        <li><a href="#">LinkedIn</a></li>
        ...
    </ul>
    

    By using <ul> and <li>, you convey the structure of your content more clearly, making it easier for screen readers and search engines to understand. Additionally, it aligns with best practices for HTML semantics.

    I hope you find this helpful!

    Keep up the excellent work!

    Marked as helpful
  • Bernardo Poggioni•7,030
    @R3ygoski
    Posted over 1 year ago

    Здравей zh4r, I'd like to congratulate you on completing your project. It turned out really well and quite original. It's always refreshing to see original projects on this platform. My sincere congratulations!

    Regarding your question about meta tags, I have a few suggestions. You could also consider adding og and twitter meta tags, but it's just a suggestion.

    Now, about the semantic (and consequently accessibility) aspect of your HTML, I have some suggestions for improvement. They are:

    • <div class="card">: This <div> could be replaced by an <article> tag, as the content here is independent and self-explanatory.
    • <div class="links">: Instead of using a <div>, you could use a <ul> with <li> elements, as these buttons form a list since they share many similar characteristics.
    • <div class="pv">: Instead of using a <div> here, you could use a <section>, as the content is thematically related to each other; they are all related to the profile.
    • <h2>Sofia City, Bulgaria</h2>: The correct tag here wouldn't be an <h2>, but rather an <address>. This way, you would be indicating that it's an address.

    Once again, congratulations on the creativity in approaching the challenge in a unique way. Keep practicing and improving. If anything I said isn't clear, please comment below, and I'll try to help as best as possible.

    Marked as helpful
  • zh4r•150
    @zh4r
    Posted over 1 year ago

    @R3ygoski, Video was very well done, did the job beautifully.

    I think I've achieved everything I aimed for in this challenge! I'll see you guys in the next one, hehe <3

  • zh4r•150
    @zh4r
    Posted over 1 year ago

    @0xabdulkhalid @R3ygoski @danielmrz-dev I'm proud to say I've added all of your suggestions and everything looks much better!

    I'll need to look deeper into @0xabdulkhalid's grid suggestion to understand it better.

    Thank you all again for your kind words and constructive criticism, it's much appreciated!

    Cheers!

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

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

Oops! 😬

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

Log in with GitHub