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

Social Links Profile solution with simple HTML and CSS

jabnakar•20
@jabnakar
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey there! 👋 Just finished working on a social links card visual for a Frontend Mentor challenge. I'd really appreciate your feedback on the HTML and CSS code. Specifically looking for thoughts on the overall design, how it renders on different screens, and any ideas on code improvement. If you notice any have tips on best practices, I'm all ears! Thanks a bunch for your time and input!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stefan Bojkovski•720
    @xStephx
    Posted over 1 year ago

    Hello,

    Your solution looks great, I have some suggestions for better coding practice and organization.

    The first suggestion is to write your HTML and CSS in separate files for better overview, organization and practice.

    The second suggestion is to use semantic tags for better accessibility, better organization.

    The third suggestion is to use a Grid or Flexbox for centering and alignment system, this method is a quick and easy, time-effective.

    The fourth suggestion is on social media buttons in this project to add hover for a better looking.

    Have a nice coding!

    Marked as helpful
  • Caaspita•170
    @Caaspita
    Posted over 1 year ago

    Congrats for the new solutions, i have some sugestions for you.

    -It would be good to separate the CSS and the HTML into different files to maintain good practice and more organized code.

    -Try to maintain correct indentation in the code so that it is easier to read it for you and other people

    -You could improve good practices by using semantic HTML so that the browser can read your website better. I leave you this page that explains it better. https://www.freecodecamp.org/news/semantic-html5-elements/

    Cheer up and keep programming

    Marked as helpful
  • Ayua Michael•530
    @TorCanHack
    Posted over 1 year ago

    Hello Funtikar, congratulations on finishing the challenge 👏🏽 🎉.

    It's beautifully done.

    Just a little observation however. I noticed the first heading is a h2 element in your webpage. Structure wise, It's a better approach to start with a h1 tag then work your way down. This is for structural and accessibiilty reasons.

    You can always customize your headers element to the font size you prefer.

    someone once gave me this advice on this platform:

    Unlike what most people think, it's not just about the size and weight of the text It is about maintaining a clear and consistent hierarchy through out the document

    Great work!

    I hope you find this helpful.

    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