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

Huddle Landing Page with Curved Sections | GRID | Flexbox

Nick OD•270
@NickODxyz
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


Hi all,

Is there a way to make the curved bg-images responsive? So you don't have to keep adding media queries everytime their hight goes out of sync.

Also has anyone got any idea how you're meant to size the gaps in the curved sections? With the figma files there is no way I can see (unless I'm missing the obvious) to get a margin / padding reference. So pretty much had to eyeball the gaps, which I'm sure won't go well lol

Any and all feedback on my work is most welcome, if you have the time.

Thanks, Nick

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 3 years ago

    Good job with this challenge, keep up the good work.

    In terms of your accessibility issues,

    • Your form fields need a label attribute with a value.

    • Your anchor tags need text in order to be clickable.

    In terms of your html validation, your css property transform requires more properties and secondly the pseudo-element :root does not exist.

    In terms of your design of the challenge

    • the paragraph below the title Build your community with fans you will love needs some space on the margin top probably around 1.1rem

    • The footer does not have a white divider line so you might want to remove that.

    I hope this helps

    Cheers, Happy coding 👍

    Marked as helpful
  • Nick OD•270
    @NickODxyz
    Posted over 3 years ago

    Oh come on now, when you visit the live site you see no gaps in my curves lol Or at least I don't :)

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.

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