Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Huddle Landing Page with curved section, using flex and js

Raza Abbas•770
@RazaAbbas62
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, just completed the huddle landing page with curved section, it first seems a much difficult to add curves but eas much easy,I have also added a little js for validating the email.

Your feedback is welcome.

thanks in advance:)

Happy coding

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Huddle landing page project! It's a significant achievement, and your code demonstrates a good understanding of HTML and CSS. Here are a few best practices recommendations for further improvement:

    1. Optimize Image Usage:

      • Consider using responsive images with srcset to load the right image size depending on the user's screen, reducing loading times on smaller devices. Learn more about responsive images here.
    2. CSS Organization:

      • Organize your CSS more efficiently. Group related properties and consider using a preprocessor like SASS for better maintainability. Also, avoid repetitive code by creating reusable classes. Learn about SASS here.
    3. JavaScript External File:

      • Move your JavaScript code into an external file. This keeps your HTML clean and makes the JavaScript easier to manage, especially as your project grows. Check out this guide for more on external scripts.

    Keep up the great work! Remember, each project is a step forward in your development journey. Stay curious and keep learning. Your progress is impressive, and I'm excited to see what you'll build next! 🌟🚀

    Marked as helpful
  • Theunis•210
    @theYuun
    Posted over 1 year ago

    A lot less white space appears in your version than in the reference image, which is ultimately for the better :)

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