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

Meet Landing Page using CUBE CSS, Flexbox & CSS GRID

accessibility, cube-css
Jordan•140
@joanFaseDev
A solution to the Meet landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


[English isn't my first language so please excuse me for any mispellings or grammatical errors]

Hi everyone :) I had a lot of fun on this project! Using a mobile first workflow seems way more natural to me (something recommanded by Kevin Powell). Working like that, one can build simple yet solid foundations and delay the more complicated stuff to the end of the project. I wonder if that way of working is the more popular one and, if not, what are the advantages of working the other way around?

There's one other question i'd like to ask concerning this project. The mobile and tablet design have a hero image and that image split up when reaching desktop design (one half to the left, one half to the right and the welcoming card to the middle) so basically one need to add an image after a particular breakpoint. To do it i created two html elements picture and made one of them invisible using display: none until the specific breakpoint was reached. I honestly feel like it's a bad method because there's an element which is useless more than half the time and can potentially misguide screen readers (not sure of what i'm writing but i always heard that one developper must have a very good reason to make an element disappear from a user ^^). So i've wondered if anyone had a better idea/solution (i'm gonna search on my own but asking can't hurt right?)

Also, on this project, even if some assets were named 'footer-image', i ended up not using footer element because i felt like the contant wasn't appropriate for it.

That's all for today. Thanks for reading, have a nice day and happy coding to all!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jordan'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.