Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

HTML e CSS com grid e Flexbox

P
Carlos Eduardo Santos Oliveira•180
@Carlos-Eduardo-S
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?

The project was very enjoyable to do, even though it took much longer than I thought it would. I was proud to have completed the project without many problems, especially problems related to Grid, and I'm also proud to have learned something new with the footer image.

What I would definitely do differently is not try to create the line and number in the circle using HTML (I don't know if it's necessary to know). Even though I managed to do it, made me waste a lot of time when I only needed to get the image from Figma.

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

The most difficult challenges I encountered in this project were the second line with the number inside the circle and the background-image of the footer.

As I mentioned above, I wasted a lot of time trying to create the line and the circle in HTML and styling them in CSS, and then I encountered the problem of not being able to change the color of the background-image or set its correct alignment.

I tried to solve this problem by watching video tutorials that weren't very helpful. I replaced the lines and circle I made with HTML and CSS with images taken from Figma. Reading documentation helped me solve the background color problem, and by testing some margin commands, I discovered that I could use a negative margin, which solved the alignment problem.

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

I would like general feedback.

In the previous project, I received help from @asia272, which helped me a lot. I tried to implement as many of her tips as possible, even though some things were missing, especially with grid.

So, I appreciate any feedback I receive on this project. It helps a lot. Thank you in advance.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Carlos Eduardo Santos Oliveira'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

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.