Skip to content
Submitted about 3 years ago

Huddle Landing Page (this took me a week)

Nguyen Nguyen•340
@jesuisbienbien
A solution to the Huddle landing page with a single introductory section challenge
Preview (opens in new tab)Code (opens in new tab)

Solution retrospective

Any feedbacks are welcome. I have some questions regarding background and fontawesome icons. 1- I tried to position my background exactly as the design, and it worked but only when I did background-size:contain. The issue is using contain, when my browser got bigger, but not big enough for desktop size yet, the background doesn't cover the whole page. I hope I explained this well enough.

2- Are we still able to use fontawesome with CDN now? or we can only use with Kit? (version 5 and up)

3- Any suggestions on how I can clean up my codes? Any recommended articles/ videos on this matter?

Thank you in advance for anyone's help. I love to learn so throw me some feedbacks please :D

Code

Please log in to post a comment

Log in

Community feedback

  • Vanza Setia•27,715
    @vanzasetia

    Hello, Nguyen! 👋

    Great work on this challenge! Your solution looks pretty good! 😀 It's great that you wrap all the page content with landmark elements! Well done! 👍

    Regarding your questions.

    1. I notice that it use background-size: cover and it works well. I used background-size: cover and it worked well. However, I had background-position: center right; and it looked similar to the design. You can see my solution if you want.
    2. Yes, you can visit cdnjs.com and grab the link tag for the Font Awesome for version six and below. But, I would recommend downloading the needed icon from the Font Awesome website instead of importing the entire icons. It is going to boost the performance of the site.

    For the third question, here are some suggestions from me.

    • Alternative text for images should not contain any words that related to image (e.g. picture, photo, logo, icon, graphic, avatar, etc). It's already an image element so the screen reader will pronounce it as an image.
    • Not all images need alternative text. In this case, I would recommend leaving the alt="" empty so that the screen reader users won't have to listen to unrelated content.

    A11y checklist would be a great resource to make your site accessible. Make sure that everytime you submit any solution you check as many items as possible.

    That's it! Hope this helps. 😊

    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