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

HTML, CSS

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

Solution retrospective


Hello! Here is my third submission on the frontendmentor.io platform. Still love the css animations as you can tell :D

Also this time I approached the coding of the project as mobile first. I must tell that it saved me a lot of headache and I had to write much less code.

Although on a landingpage like that, most likely a client does not want to present ratings that are given less than 5 stars, but I added a possibility to add every rating from one to five. These classes can be added easily with JS to the span element. For example if there is a 4 star rating you can add a class .four-stars to the span element and it will present 4 stars instead of 5.

As always, feel free to comment :) Awesome, awesome platform and community here!

Cheers, Verner

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anna Leigh•5,135
    @brasspetals
    Posted about 4 years ago

    Hello again, Verner! 👋 Sorry, I missed this one.

    Another great animation job! Also, excellent job on the responsiveness. I love how much attention you gave to the the tablet and "in between" styles. It really looks great. 👍

    Happy to hear you enjoyed doing mobile first! I agree - I think it makes life MUCH easier.

    Your HTML isn't quite semantic. A header element (and footer as well, although not used here) should not go inside a main element. Also, the error from your report is occuring because if you use a section element, you always need a heading or another label (I'll refer you back to this extensive article). This entire challenge would probably be one "section" of a full-page layout, so using things like header and main aren't really needed here. HTML semantics can be very tricky! The article I linked here is really useful, and I still go back to it often.

    Again, awesome job on this one! Happy coding!

  • mohammad•305
    @Mohammd1321
    Posted about 4 years ago

    hey man your layout awesome but i noticed you included every element literally to give them the same style there is something called universal selector which is this * instead of writing every single element in there like you did here

    html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video you can replace all of that with simply this

    • {

    }

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    Really nice job on this challenge ⭐⭐⭐⭐⭐

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

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