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

Social Media Link Page with HTML and CSS

Nicolette Reneilwe Mashaba•140
@Reney17
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?

What are you most proud of, and what would you do differently next time?

Proud of:

Successful integration of key features like social media links and responsive design. A clean, user-friendly design with accessibility features. Effective use of HTML, CSS, JavaScript, and Git for version control. What I’d do differently:

Focus more on cross-browser testing and optimization. Improve error handling and project documentation. Gather early user feedback to refine the project in real-time.

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

Cross-Browser Compatibility: Issues with styling and responsiveness across browsers. Solution: Used testing tools and CSS fixes to ensure consistency.

Version Control Issues: Problems with Git when pushing changes. Solution: Pruned remotes, deleted corrupted references, and resolved conflicts.

Missing or Broken Assets: Missing fonts and images affecting the design. Solution: Removed unnecessary files and re-uploaded missing assets.

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

Cross-Browser Compatibility Issues: Despite testing, I am still facing minor layout inconsistencies on certain browsers. I would appreciate guidance on best practices to handle these issues, particularly with CSS Grid/Flexbox.

Optimizing Mobile Responsiveness: While the website is responsive, I am looking for tips to make it even more fluid on various screen sizes, especially in the navigation and footer sections.

Git and Version Control Best Practices: I encountered issues with pushing to the remote repository due to broken references. I would like advice on managing large repositories and avoiding similar issues in the future.

Code Documentation: I’m unsure how to properly document the code for better clarity. Could I get some advice on the best practices for writing clear and concise documentation for my project?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tarun Dadlani•60
    @tarun080698
    Posted 6 months ago

    Hello! Great job on completing the solution! While it may not be pixel-perfect, it's a solid effort, and what's most important is that you're on the right path to learning, mastering your skills, and building a strong foundation. Keep going!

    For some constructive feedback, I'd recommend focusing a bit more on mastering Flexbox in CSS, especially when it comes to centering elements perfectly from all sides. Paying attention to spacing and ensuring the correct font choice will help refine the design even further.

    You're making great progress, and with a few improvements, you'll be well on your way to creating flawless designs. Keep up the fantastic work!

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