Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

HTML,CSS, Figma

P
Justin Green•2,940
@jgreen721
A solution to the Meet landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Just some more practice using Figma specs. Feels frustrating sometimes in that, doesn't always feels consistent to CSS conventions?? and in making changes with the responsiveness I found a few instances where it felt they just change the parent-child container relationship entirely and in a manner that doesn't feel reasonable/necessary. Invariably I'm almost finding the entire thing to be an absolute/left/top game and in some ways container/divs be damned, which doesn't really feel right. Would appreciate advice with anyone experienced in the design conversion process, or just any feedback/suggestions in general!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anna•545
    @NitaLewska
    Posted over 2 years ago

    Hey! =) you've done a great work completing this challenge!

    1. If it's okay, I'd suggest you to read about semantic HTML though =) Tags like <header>, <main>, <footer>, <section> and so on are really important for the aссessibility! https://www.w3schools.com/html/html5_semantic_elements.asp https://stackoverflow.com/questions/1729447/what-are-the-benefits-of-using-semantic-html

    2. What's for your question - try to follow some tutorials on Youtube, for example, so to see, how other people do it. I can't really advise you any particular vids, as I mostly watch tutorials in Russian. Anyways, in the beginning, tutorials can be a great help, as we need to learn from the best =) Just remember the main rule - not only watch, but repeat everything yourself, too!!!

    Also you can look how other people here or on GitHub solved the same challenge and try to understand what they've done and how it works =)

    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 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