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

Social links profile using FlexBox, CSS and HTML

CristianoAAA•30
@CristianoAAA
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 really proud that i could take on the challenges that i saw while coding and get the solution, one thing i would do it differently is being calmer when facing with a problem, because there's a solution and i just have to think for a little bit or seek for help that it will be all good.

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

I had some problems with making the text placement perfect because i didn't know how to make them in the right place, i thought about using flexbox, creating divs for each one of them, but after thinking a little bit i remembered i could just use margins and it worked out well. To find out the right color i used a site called color picker. To make the right adjustments to the placement of the buttons and the card i used flexbox.

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

I would like to know if my using of flexbox in the project was optimal and if there's any adjustment i need to make.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar Dwivedi•720
    @Harsh-Kumar-Dwivedi
    Posted about 1 year ago

    Hi @CristianoAAA,

    I think there needs to be some adjustment done regarding the image visibility on the webpage, what you can do is, as you have defined image source as <img src="assets/images/avatar-jessica.jpeg"/>, therefore, create a folder with the name as assets, inside that create another folder with the name as images, inside that add the avatar Jessica image with the name as avatar-jessica.jpeg and then drop the assets folder inside the github repository of this project.

    Nice Work !

    Hope it is helpful !

    Happy Coding !

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, SASS, 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