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

Responsive landing page using Flexbox and CSS Grid

accessibility
Gustavo Gutiérrez•370
@gustavo2023
A solution to the Meet landing page 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 think in general the project turned out well. When I started the project I easily managed to figure out how should I structure the HTML to make it look like I wanted. Although not everything looks exactly like the design, the structure works well.

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

The hero section was a little challenging. I wasn't sure on how to make it so that when the screen is desktop size, the section displays the two images that correspond and when the screen is table or mobile size it displays the single image that corresponds. Eventually I simply added `` elements for each image in the correct place and in the CSS I used alternated using display: none and Flex to show the images I wanted.

The other challenge was the background image in the footer and how to add the color to it. I was able to add both the image and the color, but the color doesn't look the same, I'm not sure how to fix that.

What specific areas of your project would you like help with?
  • Improvements in accessibility that I can make.
  • Are there any improvements I can make to the semantic structure of my HTML?
  • Any feedback on the best practices that I'm not following or overlooked mistakes.
  • Corrections for the hero section and the footer to make it look more like the design.
  • Is my use of CSS Grid and Flexbox efficient or what improvements could I make?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Suhas Patnaik•190
    @SuhasPatnaik
    Posted 9 months ago

    I relate to the part where my site also didn't turn out to be a pixel-perfect match to the provided design. But I'm pretty happy with the output still while being quite aware of what improvements I could make in future projects to not repeat the inaccuracies in this project.

    Onwards and upwards! 🚀

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