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

Meet Landing Challenge with CSS Grid and Flexbox

P
shruticodes01•270
@shruticodes01
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?
  • Writing semantic html.
  • Understanding CSS Grid and Flexbox.
What challenges did you encounter, and how did you overcome them?
  • Aligning images correctly using object-position.
  • I used background-blend-mode to blend the background color and image.
What specific areas of your project would you like help with?
  • The footer background is not the same color as the design, the cyan background seems a lot darker. How could I reach the same result?

  • Is there any way to avoid media-queries on changing margins and padding? Or size of the images? I tried to use min() and calc() but did not get me the right results. So I used media-queries.

  • How else could improve my code?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hussein Malkawi•120
    @r4w311a
    Posted 7 months ago

    Well done!

  • Adam•340
    @nadam-design
    Posted 7 months ago

    Hi @cookie-monster01!

    You’ve done an excellent job! Here are a few small things I noticed:

    • Buttons: On hover, the cursor doesn’t change to indicate that the element is clickable. In this case, it might be more effective to use an anchor (<a>) instead of a button, as it provides clearer feedback to the user.
    • Section numbering: The outline color differs from what’s shown in the design.
    • Images: Instead of using object-fit: fill;, try object-fit: cover;. This will help avoid image distortion, especially on smaller viewport sizes (currently, images get distorted in such cases).

    Keep up the great work—go for it!

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