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

Mobile first site using HTML, CSS, Flexbox, and SASS

P
Isaac Novaes•650
@isaacnovaes
A solution to the Huddle landing page with curved sections challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey! Check out my second solution! 😀

I didn't noticed any major mistakes, but if you do, please let me know.

Happy coding! 😁

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, great work on this one. The layout in desktop is fine and the mobile state as well.

    Some suggestions would be that:

    1. I think you are rendering the wrong font in here, you might want to check that one out.

    2. The text-alignment are somewhat not proportional to other. Since for every text-section you are using, you apply text-align: center to them which is not really on the design. They need to be on the left side and also, you might want to adjust the width capping. On the original, the text are somehow longer than you are using, so adjusting the width on those will be really good.

    3. The social media icons on the footer needs to be wrapped inside a tags, since they are links right, so nesting them is good.

    4. Your form on the mobile state, it is on the right side, which I think should not be the case, or am I wrong, I haven't really tackle this one. But check that one out as well. But I am glad that you made another html on the form submission^

    But still, really good job on this^

  • P
    Isaac Novaes•650
    @isaacnovaes
    Posted about 4 years ago

    Hello, pikamart!

    First of all, thank you for your feedback, I really appreciate it.

    Here are my comments on your suggestions:

    1. You are totally right because the font rendered was a sans-serif fallback, not the Poppins font. This mistake is already fixed in the new version of the site.

    2. For the mobile version, the text alignment should be center. However, for the desktop version, it should be left. I just forgot to make this conversion. Mistake fixed, too.

    3. Yep, I agree with you. Mistake fixed.

    4. According to the original challenge design, the form inputs should be right-aligned. So I think that my solution is appropriate.

    Once again, thank you for your feedback.

    I ask you to check the new version of my solution. If you find something else, please let me know.

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

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