Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Huddle landing page with alternating feature blocks

👾 Ekaterine Mitagvaria 👾•7,860
@catherineisonline
A solution to the Huddle landing page with alternating feature blocks challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, Frontend Mentor community! This is my solution to the Huddle landing page with alternating feature blocks.

I appreciate all the feedback you left that helped me to improve this project. Due to the fact that I published this project very long ago, I am no longer updating it and changing its status to Public Archive on my Github.

You are free to download or use the code for reference in your projects, but I no longer update it or accept any feedback.

Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted over 2 years ago

    Hey there! 👋 Here are some suggestions to help improve your code:

    • Your "buttons" were created with the incorrect element. When the user clicks on the button they should directed to a different part of you site to sign up. The Anchor Tag will achieve this.
    • The article element is not needed in this challenge, since nothing is site is independently reusable.
    • The “Illustrations” serve no other purpose than to be decorative; They add no value. Their Alt Tag should left blank and have an aria-hidden=“true” to hides it from assistive technology.
    • The "Ready To Build Your Community?" should be a h2 heading.
    • As mentioned by the other user, the footer “phone” and “address” should be wrapped in Anchor Tags, so users can easily click on them and have the appropriate app open for them.
    • The footer links need to be wrapped inside a nav element and should only be one single list.
    • The “social media icons” are not decorative, they need to have an Alt Tag with a description.

    If you have any questions or need further clarification, feel free to reach out to me.

    Happy Coding! 🍂🦃

    Marked as helpful
  • Yehan Nilanga•670
    @Yehan20
    Posted over 2 years ago

    Congratulations on finishing the challenge, your solution looks amazing. I was wondering whether the email and number on the footer needs to be links or not , so when someone hovers, they can call or send a mail.

    Marked as helpful
  • Pranshu Sahu•770
    @Pranshu-Sahu
    Posted over 2 years ago

    Hi @catherineisonline,

    I am very impressed by the solution.

    I wanted to know that how much time did it take you to complete such pixel perfect solution and at what screen do you make your solution for desktop screen.

  • Chams•160
    @Chams-sat
    Posted over 2 years ago

    Hi .. congratulations for completing this challenge and I am very impressed by the solution. it's a pixel perfect 👌 💯

  • Jahongir Murodboev•180
    @jahongirdev
    Posted over 2 years ago

    Hi, how you creating without any errors?

  • Arash Kazerouni•140
    @arashKazerouni
    Posted over 2 years ago

    Congratulations! this is exact the same as desired design!! my solutions always have some differences with original design(even small differences, but your solution is completely fit). how did you do this?

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

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub