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

Social Links Profile Card

DanielJamesPM•30
@Danieljamespm
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 didn't know I could turn a P tag into a container itself to be able to center the text with flexbox. Making the process easier by separating the card into 3 parts. The picture with the name and location, the little quote, and a section for all the "buttons" to go into. That made it easier to separate them and get the spacing right and independent from the other sections. Also, takin advice someone gave me from my last project to make it more responsive to smaller view ports. I took that advice and double checked that everything still looked good on a smaller view port and wasn't cut off.

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

At first it was trying to get the text centered in the buttons. If i added padding or margin it made the buttons get wonky so figuring out that I can make a P tag its own container and center it with flexbox like I do everything else was great!

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

I am just trying to get more comfortable with flexbox and what it can do, but it's the easiest way to move things around and get things centered. As I get through the challenges I am trying to remember what worked and what didn't so I am not just doing so much trial and error and hoping to complete the projects quicker. They definitely shouldnt take as long as they do sometimes because there isn't much too them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chimi Rinzin•890
    @ChimiRinzin-HWR
    Posted 10 months ago

    Great work and great reflections. From as much as I have understood html until now, all of the elements can be turned into a container and can have their properties modified easily just like one another. Except for the time I had difficulties doing the same with <span> elements. If you are trying to use span as a whole single element without another direct element to encase it, keep in mind that you mind face some difficulties and would take time to reach your goals.

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