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

Responsive Centered Profile

Mohammad-Moneer•120
@Mohammad-Moneer
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?

Here are some aspects that I am proud of:

  • Building an organized structure and using the unordered list element `` to group the links together, which makes them easy to control.
  • Using CSS variables for color management, which enhances maintainability and readability.
  • Getting familiar with media queries, which I used several times in this project to implement responsive design and ensure the profile page looks good on various devices.
  • Adding hover, focus, and active states for links, improving user interaction feedback.

As for what I would do differently next time:

I really don't know exactly, but I am open-minded to any suggestions if available.

What challenges did you encounter, and how did you overcome them?
  • Horizontal Scroll Issue: Initially, a horizontal scrollbar was appearing due to the use of width: 100vw. This was resolved by changing it to width: 100%.
  • Vertical Spacing: Adjusting the vertical padding to ensure the profile section was not too close to the top of the viewport, and maintaining consistency across different screen sizes.
What specific areas of your project would you like help with?

I just need some review on the link states styles to ensure this approach is correct: CSS .profile .profile-info ul li a:link, .profile .profile-info ul li a:visited, .profile .profile-info ul li a:focus { background-color: var(--grey); }

.profile .profile-info ul li a:hover { background-color: var(--light-grey); }

.profile .profile-info ul li a:active { background-color: var(--green); color: var(--off-black); }

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Darkstar•1,420
    @DarkstarXDD
    Posted about 1 year ago
    • Avoid using complex selectors where you use class + element name to select an element. Such as profile .profile-info ul li a. You can run into specificity issues as projects become larger. It also becomes harder to debug anything when the selector looks like that. Just give any element you want to style a class name and style that class.
    Marked as helpful

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

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