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

flexbox ,margin, padding , justify-content, align-items, list-style

Mohamedibrahim0419•100
@Mohamedibrahim0419
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?

Simple and elegant design: ✨

The code reflects a good understanding of formatting elements using Flexbox and applying colors in an attractive way. 🎨 Using effects such as changing the color and background on hover shows interest in the user experience. 🚀 Organization of the code: 📂

The code is organized and understandable, making it easy to read and edit. 🛠️ Dividing elements such as .card, .profile, and ul li a makes the code easy to customize. 📋 What could be improved next time: 🔧 Add comments: 📝

Code annotations can be added to explain the purpose of each part, making it easier to collaborate with others. 🤝 Improve scalability: 🔄

It might be a good idea to use CSS variables (:root) to define colors and fonts. This will allow for easier design changes in the future. 🎯 Add responsiveness: 📱

Although the code supports flexibility in display using Flexbox, the design can be improved to be more suitable for different screen sizes using media queries. 🌐 Reduce duplication: ➖

Create general CSS rules to avoid duplicating similar styles, such as rules for margin and padding. 🎛️ Improve accessibility: ♿

Add attributes like alt to images and place greater emphasis on contrast between text colors and backgrounds. 🕶️

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

Formatting elements using Flexbox 🔄 Challenge: You may have struggled to make elements within the card, such as text and images, consistent and centered. How I overcame it: I relied on Flexbox effectively, using properties like justify-content and align-items to ensure good centering of elements. Make the code organized and easy to read 📂 Challenge: Organizing code can be a challenge, especially when there are many elements and styles. How I overcame it: I named classes clearly, such as .card and .profile, which made it easier to understand the purpose of each part.

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

Add interactive features using JavaScript: ⚡

Incorporate interactive elements, such as showing or hiding content on scrolling or clicking.

Improve response to events such as pressing buttons or moving elements

Test the project and ensure it is free of errors: 🧪

Ask for help in testing the project and discovering errors or issues. Improve performance based on feedback.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mohamedibrahim0419'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.