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

Social Links Profile Challenge

sass/scss, tailwind-css, bootstrap
MD Rohejul Islam Hemal•60
@hemal6325
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’m most proud of completing the project successfully with all key features implemented and working smoothly, especially under tight deadlines. It was rewarding to see the idea come to life and provide value to users. If I were to do it again, I would spend more time in the planning and design phase to avoid some of the rushed decisions made during development, and I’d focus on better time management and earlier testing to catch issues sooner.

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

One of the biggest challenges I faced was handling unexpected technical issues, such as bugs and integration conflicts between different modules. I also struggled at times with managing the workload and meeting deadlines. To overcome these, I broke tasks into smaller, manageable steps, used version control effectively, and actively sought help from team members and online communities. Regular check-ins and testing also helped identify problems early and keep the project on track.

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

I would like help with improving the UI/UX design to make the project more user-friendly and visually polished. Additionally, I’d appreciate guidance on performance optimization, advanced feature implementation, and best practices for testing and debugging to ensure the project is scalable, efficient, and maintainable in the long term.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mustafa Sen•3,180
    @mustafasen97
    Posted about 2 months ago

    The design is very good. I only have a few suggestions.

    First, try reducing the size of the image a little. For example, you can give it a width and height of 90px.

    You can also reduce the width of the card a little.

    These 2 changes you will make will create a better image.

    By the way, you tried to center the design with display: flex; but it was not centered. Then you added margin-top to the .card-body class. Delete the margin-top: 125px; code from the .card-body class.

    Then when you go to the body and add min-height: 100vh; your design will be centered vertically as well.

    You have added a transition to the buttons, which is a good thing. You may not think of much visual change for such a design. However, as the design grows, it can be more original and you can create more stylish images with different animations.

    By the way, when I looked at your codes, I saw that you used too many divs in the HTML section. I recommend that you research semantic HTML elements such as section and article instead of div. When you understand the meanings of these tags and where to use them, a more meaningful and practical code structure will emerge.

    Semantic HTML Example

    <body>
      <header>...</header>
      <main>
        <section>
          <article>...</article>
          <article>...</article>
        </section>
        <aside>...</aside>
      </main>
      <footer>...</footer>
    </body>
    

    Apart from this, most of the things in your design are very good. Your code structure will become simpler as you practice. Keep designing. Good luck in your future designs.

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