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

Responsive landing page using Grid and Flexbox

P
Peetawit Vongchanapibul•180
@pete13232
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 very proud that I was able to apply many things I've learned from previous projects. It feels great to see how those small lessons added up and helped me complete this one more confidently.

If I were to do it again, I’d probably spend a bit more time planning the layout structure before jumping into coding. That could save time in the long run and help keep the code cleaner.

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

One of the main challenges I faced was building the layout for the entire screen. Most of my previous challenges involved single components, so this was my first time working on a full-page layout.

To overcome this, I started by creating a rough wireframe using basic HTML and CSS. This helped me visualize the overall structure and plan how the layout should be divided. It gave me a clearer direction before diving into the actual styling and fine-tuning the details.

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

I tried to work around making the .hero__avatar slightly overflow out of the screen (just like in the original design), but I couldn’t quite get it right. 😭

If anyone has tips or knows how to achieve that effect properly with CSS, I’d really appreciate the help!

Thanks in advance! 🙏

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • lucigarpe•110
    @lucigarpe
    Posted about 2 months ago

    good job

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