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

Meet Landing Page responsive with HTML/CSS !

bem
Luqman (Luke)•320
@luqmanx1998
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?

A new week, a new challenge !

This is my third challenge on frontend mentor, and this time, a premium one! That means I was finally able to start working with a figma file, and it was my first time as well. It's a different experience learning to convert a figma file into code, as I had to take some time to get used to it, but it also meant that I didn't have to waste so much time guessing the margins/paddings/font-sizes and all that good stuff !

If I would do something differently next time, it's once again spending less time to make it as identical to the design as possible, as sometimes it's just impractical considering I'm still learning. Also, I didn't plan this challenge very well, as I kept improvising and changing my code as I went, and I tried to keep it as simple as possible. As a result my code ended up being messy , but going forward I will take some time to plan it out more. Nonetheless, I was proud of finishing this piece, and it's beautiful to look at !

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

I encountered a few challenges, first of all with responsive images. This challenge was a bit tricky, as I learned about the limitations of the picture element, so I had to come up with a different way to replicate the desktop version of the hero after finishing the mobile/tablet version. I also had issues replicating certain parts of the layout, specifically the desktop footer ! I couldn't quite get it to match the design, and I ended up having to hard-code certain elements in the footer, but it felt like I had no choice. And the last issue I encountered was trying to position the background image to match the design. I tried using the background-position property, and played around with the values, but it usually meant creating a gap around the entire footer, leaving a white space, so I left it as it is in the end. Nonetheless, I'm really proud of this and if anyone would leave me any feedback, I would really appreciate it ! :D

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

As mentioned above, any feedback at all would be greatly appreciated !

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 Luqman (Luke)'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.