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

Meet Landing Page (Responsive Layout Flexbox, Grid, and Media Queries)

Max•260
@maxkdavis
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?
  • Taking the time to dig into the design specs and translate them into CSS custom variables
  • Using a mobile first approach and applying media queries for tablet and desktop layouts
  • Keeping code D.R.Y.
What challenges did you encounter, and how did you overcome them?
  • A few challenges with image display based on layout.
  • Need to be better about avoiding fixed dimensions and inside use dynamic metrics
What specific areas of your project would you like help with?
  • General peer review and suggestions for improvement and/or experimenting
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Maren Ehlers•230
    @MarenOelixtown
    Posted 9 months ago

    Congrats Max, your responsive design makes a good impression and you are very close to the original.

    I have noticed a few things that might be worth looking at:

    • For this use case, I would recommend using a-tags for the buttons. For download: Using the a-tag with the download attribute will instruct the browser to download the linked resource as a file. The other is just a link to a part of the page. 👉Button vs Link👈

    • The picture-element could be useful for the hero-image. You can address the desktop media-query directly in the html without css. Using the picture-element and the srcset attribute also has performance advantages. It ensures that only the necessary images are loaded depending on the screen size. 👉W3 👈 👉MDN 👈

    • In your features__content-part is the heading structure unfavourable. You have mixed headings with <h2> and <h3>, but there is no clear hierarchy. If a profile name is in <h3>, there should be a higher-level heading in <h2> first. This article explains the use of the hgroup-element, which I think also fits quite well here. 👉HTML structure 👈

    I hope it inspires you...all the best! 👋

    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