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

Huddle landing page with curved sections solution

Mohammed Fakih•1,590
@javascriptor1
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


I have used padding and margin so many times in this challenge. I played with it a lot and I can say I understand what padding and margins are. I feel very comfortable using both of them and troubleshooting any bug or misalignment of any element on the page.

I also continued to use CSS grid and great progress has been made in understanding basic properties and how to use them.

Most importantly for this challenge, I just found out how easy is to make these curvy shapes sections on a modern startup website 😃.

By doing this challenge, I have completed 40 exercises on FEM. Working with elements, alignment, and positioning was not easy when I started. However, I can see the big progress I have made in the last 6 months.

It's time to move on and start learning React. I will be starting next week, and I hope I made the same progress I did with CSS.

I would appreciate it if React developers here share with us how best to learn React in 2024, especially with new frameworks working with it like Vite and Next JS.

Built with 🛠

  • Semantic HTML5 markup ✔
  • CSS grid 🔳
  • CSS custom properties 🎨
  • CSS Flexbox 🎁
  • Mobile-first workflow 📱
  • PixelPerfect chrome extension 👌
  • Responsively ✌
  • Web ToolBox ⚒

What I learned

  • Create web page sections with curve shapes

Continued development

  • Passing arguments to functions
  • Working with CSS :nth-child() selector

Useful resources

  • CSS :nth-child() Selector

Author

  • Twitter -[https://twitter.com/javascriptor1]
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mohammed Fakih's solution.

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.