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

Meet landing page

cube-css
P
Dave Quah•650
@Milleus
A solution to the Meet landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone o/

I would appreciate if you can check this out and let me know any feedback or tips on how it can be improved, or how you might approach this differently. Thank you very much!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jim Barnett•260
    @jamesbarnett
    Posted 11 months ago

    Hello Dave,

    Your solution is excellent and I will be bookmarking it! I don't really have any suggestions on how to improve your solution, but you mentioned alternative approaches, so I will outline a couple of things I did differently.

    Having just finished this challenge, I immediately went to look at your implementation of the vertical line/circled section number element. I find your solution quite elegant. I took a different approach and used pseudo elements. I think your way is better, especially with the aria-hidden=true.

    The next thing I wanted to look at was your hero, and again here, I liked your implementation better than my own. Mine was just media queries and pseudo elements.

    I liked the way you did the tinted footer image. My approach used linear-gradients and multiple backgrounds, described here: https://css-tricks.com/tinted-images-multiple-backgrounds/

    I learned a lot and found some things to research. It was a joy to review. Happy coding!

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