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

Responsive Meet landing page HTML/CSS

P
Kyle Mulqueen•400
@kmulqueen
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'm most proud of finding a clean solution for the hero section with the overlapping images. By restructuring the HTML and using CSS Grid effectively, I achieved the visual effect without resorting to absolute positioning or other hacky techniques. Next time, I would start with a more thorough analysis of the desktop layout before writing any HTML structure. This would have saved me from having to refactor my code after realizing my initial structure wouldn't work for all viewports.

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

The biggest challenge was positioning the hero images to extend slightly beyond their containers without causing horizontal scrolling. Initial approaches using transforms or negative margins created unwanted scrollbars. I overcame this by:

  1. Restructuring my HTML to create a better foundation
  2. Using a grid layout with precise control over image sizing
  3. Learning about browser-specific overflow properties
  4. Using the justify-self property to position elements within their grid cells

Another challenge was applying a colored overlay to images. I solved this with pseudo-elements and CSS variables rather than directly modifying the images, which maintained better separation of concerns.

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

I'd appreciate feedback on:

  1. Performance optimization for the responsive images implementation
  2. Best practices for cross-browser compatibility, especially for overflow handling
  3. Ways to improve accessibility for the text overlaid on images
  4. More elegant solutions for creating spacing between grid items
  5. Techniques for testing that the correct responsive images are loading at different breakpoints
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kyle Mulqueen's solution.

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.