Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Meet Landing Page

P
Jan Kotvaš•460
@DrakeHermit
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 am proud of myself that I managed to finish this challenge. This was my first time working with responsiveness across 3 different viewports and even though I managed to make it look decent I still have ways to go, my breakpoints just aren't perfect enough. It's either cuz I used absolute width declaration or I'm not totally sure. When I hit the breakpoints and stay there it looks good but adjusting the viewport makes some of my elements break.

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

The main challenge I encountered was with showing and hiding header and footer pictures based on the viewport. I did manage to make it work with time, but I would love to know if there's a better way to do this without using JS. Also making the design look good across all 3 different viewports proved a challenge which I didn't anticipate at all.

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

I still struggle with accessibility, and I can already imagine people that look at my CSS scratching their heads trying to figure out what does what. I need to work on structuring my code a lot more. I would love if someone could point me in a good direction on how to structure my CSS, and probably my HTML too(accessibility wise).

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Koda👹•3,830
    @kodan96
    Posted about 1 year ago

    hi there! 👋

    • When you structure your css code just look for repetitiveness in the page's layout.

    • apply basic typography to your tag selectors, so there's no need to re-write all of these everytime you encounter a new <p> element for example.

    • after applying these you can use attribute classes if necessary to give these their unique values after setting up a base for them.

    • also you can look up BEM notation, it's a popular naming convention in web dev.

    Hope this helps 🙏

    Good luck and happy coding! 💪

    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