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

Responsive landing page using HTML and CSS

Solomon Yahwin•40
@Auto-Yahwin
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please let me know how how it looks and how to improve it. I'd really appreciate your feedback, thanks.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kareemah Ajina•120
    @Kareemah-codes
    Posted over 3 years ago

    Hello, you did great. Here are a few notes I have:

    1. Try to make your class names more readable. Naming them "class4" or" class5" doesn't make the CSS easy to read by you and others. Something I like to keep in mind when naming classes is to give them names that describe what they do.
    2. Use google fonts, I think the font for this challenge is Roboto. That's about it!
    Marked as helpful
  • Ines Riahi•110
    @inesriahi
    Posted over 3 years ago

    Great Work! There is a style guiding file attached to the downloaded files. You can use it to set the colors and font as given.

    Marked as helpful
  • Kareemah Ajina•120
    @Kareemah-codes
    Posted over 3 years ago

    Hi !, I am glad my feedback was helpful. So for the font, It is really quite easy. Here are the steps you should take:

    1. Click the link.
    2. To your right, there will be some sort of menu. Look towards where you have "link" and "import". Side note: "link" is for if you want to enable the font through your HTML file, while "import" is for the CSS file. They both do the same thing, so you can pick anyone, but I prefer to use import and put it in the CSS file(I also notice it is the same for other people I know). If you prefer to use CSS, good design practice is to put the @import link as the first thing on your CSS file.
    3. Once you are done with this, copy the CSS styling and paste it into your CSS file or style tag.

    Voila!, you are done. I would advise going to the google font website (https://fonts.google.com/) and trying to implement a font of your choice for a previous project you have done, just so the process sticks. Try reading this article for a better explanation, https://www.freecodecamp.org/news/how-to-use-google-fonts-in-your-next-web-design-project-e1ad48f1adfa/

    Marked as helpful

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