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

Responsive site using CSS Grid

Mitchell Gould•250
@helphop
A solution to the PayAPI multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had some challenge placing the circles. I think I've worked it out the way I have done it but if anyone has other suggestions I would welcome them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mitchell Gould•250
    @helphop
    Posted over 4 years ago

    Excellent. I will do as you suggest. Thanks again.

  • Mitchell Gould•250
    @helphop
    Posted over 4 years ago

    Hey Matt,

    Thank you very much for your awesome feedback. I really appreciate you taking the time to have a look at the site and reflect on some ways I can improve. I agree I have to bite the bullet and do some client side validations using JS. I have been focusing more on improving my css skills so I kinda punted that the JS work.

    I have a question about feedback. I have not received much feedback from the community about my work so far. This is in fact the first time I am receiving feedback and I really appreciate it. What I would like even more and would be willing to pay for is to go over my work with someone on your team to discuss other ways to improve my code so that I can really push the usefulness of these exercises and get the most out of them.

    Does FrontendMentor provide any services like this?

    Best, Mitch

  • Matt Studdert•13,611
    @mattstuddert
    Posted over 4 years ago

    Awesome work on this challenge, Mitchell. Nice to see you diving in at the deep end with such a big project as your first challenge! Did you learn anything new while working through it?

    After looking at your project, here are some pointers:

    • I'd recommend reviewing the solution report and try resolving those issues
    • Your forms currently don't have any client-side validation. I'd recommend trying to implement this using the active state designs as a reference. Form validation is a common development task, so it's definitely worth practising
    • You've set the alt text for the logo to the word "logo". This doesn't help describe the image for screen reader users. As it's a logo image, the name of the company/site would be best. So you could update that to say "Pay API".

    It's great to see you using the picture element for responsive imagery. The general responsiveness of your layouts looks good too and it's great to see you using min-width media queries.

    I hope that helps. Keep up the great work! 👍

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

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