Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

meet-landing-page using css from scratch

Christ Kevin Touga Watat•270
@Christ-Kevin
A solution to the Meet landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Do you guys think that It was a good Idea, when I decided to give a width higher than 100% to the container of my image so that it overlapps his parent (body). Do you guys think there is something in my project that I could do better.

I thankyou for every comment that could make me improve my coding skills.

Kind regards

Christ

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hello there! 👋

    Congratulations on finishing this challenge! 🎉

    Good job on using the width and height attributes for the img elements! This way, the browser knows how much space the image requires before it can be fully loaded. As a result, it would optimize CLS (Cumulative Layout Shift).

    I notice that the HTML has two link tags for the stylesheet. But, the typography.css doesn't exist in the assets/styles/ folder. So, I would recommend uploading or pushing the necessary CSS file for the site.

    Regarding the image, are you talking about the image-hero? For the image-hero, I made those as background images on all screen sizes.

    Some more suggestions for improvements.

    • Write your code with a consistent style (e.g. the indentation, quotes, whitespace, etc) or use code-formatter (e.g. Prettier). If you write or format your code that way, it will make it easier to read for everyone (including your future self).
    • The download button should be an anchor tag with download attribute (not a button).
    • I would recommend making the number between sections ( <aside>01</aside>) with pseudo-elements. It is possible to create those with pure CSS. As a result, it will clean up the HTML from the decorative elements.

    That's it! I hope this helps! 🙂

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub