Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

Responsive landing page using CSS, JAvascript and Html

akinwale01•50
@akinwale01
A solution to the Product list with cart challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I was able to devote my time into doing it. Took lots of hours but I got it at the end. Learnt new Javascript functions, and attributes.

What challenges did you encounter, and how did you overcome them?

I was discouraged when I got to how to make the cart-summary change to hold items. And also how to style the confirm-order

What specific areas of your project would you like help with?

In all areas. If there is any part of the project that needs correcting. Would gladly accept it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,460
    @dylan-dot-c
    Posted 8 months ago

    Well done, I can help you with this!

    • The font: Currently it seems you didn't use the font specified in style-guide.md as the browser is using the default and ugly Time New Romans font. You can use google fonts to get the one you want and import it via your CSS or HTML file.
    • Responsiveness: The website looks good on desktops but that's just about it(no offense). I suggest doing a mobile-first approach that helps to make building it easier especially since in most cases mobile designs are easier and faster to implement and also it's easier to scale your design up than down.
    • Accessibility: All buttons seems to be focusable but on the increment and decrement buttons you need to add a focus style as a user can't really see where the keyboard tab is currently at when they are on that element. I also find it weird that you have the containers in that order. You should also make use of the main tag to help make it more semantic and remove that landmark error you have up there^^^. Also it's weird to have the overlay as a separate div from the modal-container as you could just remove it and use a background-color on the modal or put the modal in the overlay.
    • Modal: When it is open, you can actually make the body/html tag an overflow of hidden as to prevent the webpage from scrolling while showing the modal.
    • Layout: For the order-summary and the order-items container you could make the container for both of those and use flex to align them in rows(default) and (columns) for mobile. Make sure that the order-summary comes after the order-items.

    There may be a few more things to discuss but these are a good starting point, you should also try using the picture element to dynamically change the images in respect to screen size. ALso you need to clean up your folder structure and actually put all the images in an images folder.

    You can check out my solution and see how I did a few things(I used vue tho) but the HTML should be similar.

    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
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