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

Huddle Landing Page

Steve Mogan Odumbe•380
@StevetheRebel
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?

Done with the task in under 12 hours. Building up my speed. Super proud on how I've been able to make it even responsive for smartwatch viewing🤩.

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

Making sure the curves seemed seamless cause some trouble but managed to learn something called vertical aligning in CSS that managed to solve my problem.

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

OMG, when trying to solve the section where the email input is invalid and shows that little red statement, extra hard. Tried even gpt but to no avail. I NEED HELP.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • haquanq•1,895
    @haquanq
    Posted about 1 year ago

    Hello @StevetheRebel 👋👋

    Congrats on completing the challenge, although it lacks some JavaScript to make the email form functions properly as the challenge stated.

    Here is my opinion:

    • To show the error message on invalid input, you need to use JavaScript (HTML & CSS alone won't make it)
    • I noticed that you have used Chat GPT to ask question, i would advise you to stay away from it, only when you have experience with the issue then Chat GPT will be your sidekick to search for information faster.

    Hope this help 🐸🐸

    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