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

My Social Links Profile Solution

P
Jocelyne Teles•180
@JocelyneTeles98
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 think I applied all the suggestions that I received from the last challenges, which makes me happy because it demonstrates that I'm understanding the information that good programmers provided me (thank you @Stroudy and @briangesteban).

Also, I applied a little bit of creativity and added a funny quote about me to describe me better, as this project has the advantage of being like a "presentation card" 😂.

For next projects, I hope to do the things with more autonomy in the sense of doing repetitive lines of code by memory (like the CSS reset, for example).

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

I have questioned myself if it was better to have HTML buttons tags () or hyperlinks tags (). I did a little bit of research, and I found a suggestion from freeCodeCamp on using the hyperlinks and then give them the desired style with the CSS file. I don't know if there are better ways to do it, but at least this solution worked well considering I'm using HTML and CSS exclusively.

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

I think, for this time, I didn't have major issues that much, but I'm still open to suggestions to improve code in general, and I will very grateful with them 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • JxPV5•30
    @JxPV5
    Posted 9 months ago

    The result is very good! I think there are too much divs, but it doesn't really change much and I'm not experienced enough to say if it's a bad practice. I'd also use a list for the buttons instead of only <a> tags but it pretty much ends up the same way either way. I'm not an expert so take this with a grain of salt I guess

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