Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

HTML&CSS, Git&Gitflow, Flebox, and Positioning

Have-Samuel•390
@Have-Samuel
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Guy,

Hope you are well. Ideas, suggestions, and comments are welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David Rodriguez B.•430
    @davidFreelance19
    Posted over 2 years ago

    Hello developer! Congratulations on completing this challenge. I have seen your code and bring you some tips and improvements on your code! (Only for desktop layout)

    body {
         display: flex;
         align-items: center;
         height: 100vh;
    }
    .container{
         width: 100%;
    }
    .starts{
         padding: 0;
         display: flex;
         flex-direction: column;
         width: 100%;
    }
    .starts-units{
         display: flex;
         align-items: center;
         justify-content: space-around;
         align-items: center;
         margin-left:0
    }
    .extension-1{
         align-self: center;
    }
    .extension-2{
        align-self: end;
    }
    

    I recommend you study the display flex themes a little more, we can't always use margin or padding to be able to replicate a design. Also this will help you to have a cleaner and easier to maintain code. I hope my suggestions help you, take care!

    David Rodriguez

    Marked as helpful
  • Have-Samuel•390
    @Have-Samuel
    Posted over 2 years ago

    Thank you, David, That was helpful I will be looking forward to more ideas like that.

    Cheers Have

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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