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

Huddle Landing Page with Curved Sections [HTML, SCSS, Vite, Validator]

accessibility, sass/scss, vite
Tharun Raj•1,330
@Code-Beaker
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


What are you most proud of, and what would you do differently next time?

This is one of the best projects I've attempted to do so far!

I had a lot of fun building this one. It is also because of the use of SCSS which made things a lot easier. I had attempted to complete it a month ago. But, at that time, it seemed a little too complicated. But, today I managed to complete it and I'm proud of myself! I understood the fact that compiling SCSS with Vite is better when compared to using the Live Sass Compile extension as Vite requires zero configuration.

I followed the mobile-first workflow to build this project as it is recommended by many developers and some Frontend Mentor community members. It did increase the speed of my workflow so I'm glad of following it. I also used Validator to check input for email. It is really a lifesaver as I don't have to write the JS from scratch.

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

I did find it a little hard to get those curves correctly positioned. I have almost completely abandoned using pixels in my CSS. But these curves really made me use pixels because with rem I would have to change it many times.

I feel like the buttons have a poor contrast ratio. I tested it using my Firefox developer tools and it did show a warning. As for now, I'm keeping it as it is. But, I will surely change it later.

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

I would like to know if there is a better way to implement the curves. I feel like mine is pretty messed up when resizing the browser window. It always confuses me. If you have a better way, please feel free to share it. It will help me a lot.

Any suggestion is welcome, Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lokesh S•260
    @lokesh-weby
    Posted about 1 year ago

    Sounds good.. 🔥

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