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

Responsive Huddle landing page with curved sections

Luis paz•390
@Pazispeace
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


aaaah >_<! This was a challenging one because of the curves! However, somehow I managed to do it on my own with what I have learned before :-)! (I have a rule that I can't look for the solution on the internet until I solve it on my own, if it's been more than 40 minutes and I really can't, then I look for the solution. But this way I put pressure on myself to think more in the moment of solving something)

I think I wrote more css than normal (what do you think?) ... I had to make some changes on my html when I was almost finishing an I messed it up XDDDD so I had to change some class names here and there and well, that´s it.

On the other hand, the feedback you leave is really helpful!, bit by bit I´ve been learning a lot (I think? 0.0) thanks to you too, guys!

As a funny side note ("funny"): I didn't know it was allowed to use frameworks in your projects!! D: When i finish all the free html and css challenges, and start those containing JS I will start trying different frameworks! I am excited!

and as always:

Also thanks to everyone for taking the time to read and see my solution, and to those who provide feedback! It is greatly apreciated

So if you have any advices on how I can improve my choices and the way I write my code, I would greatly appreciate it!

Thanks in advance :D! Have a nice day! :=)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted about 3 years ago

    Heyo,

    This looks fantastic! Everything looks precise and neat, on all screen widths. I really love to see solutions where it's clear someone worked hard for the results. ^_^

    I looked at the html and the css too, they're both very clean and easy to read. The only thing I could really suggest here (purely because nitpicking is my hobby) is to add some inline padding to the "Try it free" button in the header. That's about it >.<

    Have you tried scss? When doing these full-page challenges css really drags on. That's when I started doing scss and it made things a lot more bearable.

    And well done, on the curves, they look real nice. It's always nice to try finding solutions on your own first! But yeah, it's good to know when to give up and ask for help/look for a hint. I used to be so adamant on doing everything on my own and considered asking for help "cheating". I was very wrong and wasted a lot of time XD

    Well done again, Luis and happy coding ^_^

    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

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