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

I try to use just CSS to add some styles

Nikita•120
@nyakita
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


That was my third project, I try to do my best in order to follow the design pattern and fill it completelly, I also used only CSS and add some design responsiveness, that wasn't so tough, but I was stuck with fonts, because I couldn't add some weight to my heading and I couldn't make text wider like in the design image. To sum up, I would say it's an awesome practise for beginners. Thank you for this opportunity.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Artur•145
    @arturpawlowski5
    Posted over 4 years ago

    Hi Nikita,

    I just made this Challenge so I have some ideas for you.

    First

    Think about using Flexbox for all your design. This way you have much more control over how each DIV will be shown on Desktop and Mobile. Right now all designs look ok on the Desktop but when you change to Mobile it not working.

    I'm sure this will take some time to understand how Flexbox works but it is standard now to use it in Design to make it more Responsive.

    Try here to know about Flexbox:

    1. A Complete Guide to Flexbox
    2. w3school
    3. MDN

    This place helps me a lot with Flexbox :).

    Some ideas for your Code

    Background IMGs

    You use now 2 Background IMGs but you do not show where they should show.

    body {
      font-size: 12px;
      font-family: 'Spartan', sans-serif;
      background-image: url("images/bg-pattern-top-mobile.svg"), url("images/bg-pattern-bottom-mobile.svg");
      background-repeat: no-repeat;
    }
    

    Try something like this to show position of this IMGs:

    #example1 {
       background-image: url(../images/bg-pattern-top-desktop.svg), url(../images/bg-pattern-bottom-desktop.svg);
      background-position: left top, right bottom;
      background-repeat: no-repeat, no-repeat;
    }
    

    More here: w3school

    Look too on your IMG files - right now you use files with Mobile in the name. You should use with Desktop in name

    Your problem with text

    You use this

    .heading {
      color: hsl(300, 43%, 22%);
      text-align: center;
      font-weight: 700;
    }
    

    If you want this text to be bigger try to add some font size e.g.

    font-size: 18px;

    Font weight you use is responsible for how "bold is text" not how big is it :)

    ** Body **

    Right now it looks like this

    body {
      font-size: 12px;
      font-family: 'Spartan', sans-serif;
      background-image: url("images/bg-pattern-top-mobile.svg"), url("images/bg-pattern-bottom-mobile.svg");
      background-repeat: no-repeat;
    }
    

    Try to add some extra line

     margin: 0; 
     padding: 0;
     height: 100vh;
    

    Margin and padding will "Delete" them from the Browser file. So your www can stretch 100% in Viewport.

    Height: 100vh will make your Project 100% Height in Viewport.

    I hope this will help little with your project.

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