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

Curated Social media Profile links menu using just HTML & CSS

Pritesh Dhandhukia•220
@pritxxh
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?

Proud Of: I'm most proud of the simplicity and efficiency of the website. By sticking to HTML and CSS, I was able to create a functional solution quickly and without unnecessary complexities.

Additionally, I'm proud of successfully achieving the core functionality of redirecting users to multiple platform profiles. This meets the primary purpose of the website effectively.

Do Differently Next Time: Next time, I would prioritize scalability from the outset. While the current solution works well for its intended purpose, planning for potential future expansions or updates would prevent the need for significant rework later on.

I would also pay closer attention to accessibility and mobile responsiveness. Ensuring the website is inclusive and optimized for various devices would enhance the user experience for all visitors.

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

Challenges: One challenge I faced was ensuring compatibility across different web browsers. Some CSS styles might render differently in various browsers, leading to inconsistencies in the website's appearance.

Another challenge was optimizing the website for speed and performance. Images, scripts, or other elements could affect load times, impacting user experience. Overcoming Challenges:

To address browser compatibility issues, I tested the website thoroughly on multiple browsers and adjusted CSS styles as needed to ensure consistency.

For optimizing speed and performance, I utilized techniques such as minification of CSS and JavaScript files, compressing images, and leveraging browser caching to improve load times.

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

Technical Expertise: I would appreciate assistance in exploring options for backend development to enhance the website's functionality while maintaining its simplicity.

Additionally, guidance on implementing JavaScript for interactivity or dynamic features could be beneficial for future iterations.

Feedback and Iteration: I'm open to receiving feedback on the current design and functionality of the website to identify areas for improvement and iterate accordingly. Suggestions for enhancing user engagement or adding features to enhance the overall user experience would also be welcomed.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Pritesh Dhandhukia's solution.

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.