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

html css

Nemanja•60
@FriendlyCodeArt
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello ! This is my first challenge on Frontend Mentor . My name is Nemanja and I am a beginer in learning HTML and CSS . I didnt finish this project because because I am not so good at responsive design, I am still learning to to that . As I said I am a begginer so any advice and feedback would be grate and very much apriciated ! Maybe you can give me some direction where to learn and what to read . Thank's you ! Thank's to this website for giving me oportunity to practise . Looking forward to new challenges !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 4 years ago

    Hi Nemanja,

    I think this looks pretty good so far, it's definitely on the way so don't be too harsh on yourself.

    I recommend you

    • try to use smaller margins and only use padding where it's needed
    • let layout grow and shrink by using flex- properties like grow, shrink and basis
    • don't overcomplicate by wrapping every line of h1 in a span, that's not necessary. Maybe give the h1 a max-width in ch units instead?
    • Remember every bit of text needs to be in a semantic element, not just a span or div
    • In alt text, you don't need to use words like 'image' because they are already announced as images.
    • Make use of the gap property to separate flex items (won't work on old browsers though, it's pretty new)
    • I always recommend against changing your html font size down to 62.5%. People do that because they think they need to always know what 1 rem is and force rems to be round numbers. It's just not necessary and can cause lots of accessibility issues.
    • If you use negative margins on elements (perfectly fine way to acheive the layout btw!) make sure you prevent overlap by giving the parent element the same amount of padding on that side (eg padding-left: -15rem on rating-container would prevent overlap)

    The biggest things that I think would help you though is starting from mobile-first. Start with the simplest layout, view it in browser with devtools open at the side. As you start to widen the viewport and think there's room to move to the desktop design, that's when you introduce your first min-width media query.

    If you take this approach, I think your css will be shorter and you'll identify layout issues sooner.

    All the best with it. Maybe try the Profile Card or Single Price Grid component if you're not feeling that confident yet. Those are both great challenges for flexbox and CSS grid, respectively 😃

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub