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

A perfect challenge for beginners

Mohamed Khaled•190
@mohamedKhaled89
A solution to the Huddle landing page with a single introductory section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my solution for the Huddle landing page.

  • Feel free to leave any feedback about my solution.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted almost 3 years ago

    Hi Mohamed Khaled,

    Another great solution. I have some suggestions regarding your solution:

    • The alternate text of the logo should not be Main Logo, it may set alt=”Huddle". Use the website's name as an alternate text.Remember that a website-logo is one of the most meaningful images on a site so use proper alt for it.
    • For social links class="social", the icons are decorative, so you should add aria-hidden=”true” to the icons, to be ignored by screen readers and to avoid redundancy and repetition.
    • Adding rel="noopener" or rel="noreferrer" totarget="_blank"links. When you link to a page on another site using target=”_blank” attribute , you can expose your site to performance and security issues.

    Hopefully this feedback helps.

    Marked as helpful
  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello Mohamed, congrats on finishing the challenge, pretty good job and it looks that your page is fully responsive, great!

    If you don't mind I would like to give you some feedback.

    It would make your application look smoother and more beautifull if you add some transitions on your buttons and social media icons when hovering, you could add something like transition: all 0.5s ease;, remember to add them inside the class and not in the :hover pseudoclass, I think this is just a little change but will be a boost for the user experience.

    Also would recommend you to use more semantic tags like section or article instead of just dividing all of your main with divs, it will boost the accesibility of your page and also the search engines will position your web better.

    Hope my feedback helps you, great job and keep it going, almost pixel perfect!

    Marked as helpful
  • Adam M•550
    @AdamMzkr
    Posted almost 3 years ago

    Good Job but, in mobile view your design as a little bit to big. To see all content you need to scroll horizontally. I think change width container to 90% will 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
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

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