Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Huddle landing page Using CSS FlexBox & Custom CSS

P
Skyz Walker•1,215
@Skyz03
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


I accomplish Responsiveness using CSS Flex-box for most of the content Thanks to @tediko for helping with my problem of social-icons. This is such a great community.✌

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • tediko•6,700
    @tediko
    Posted about 4 years ago

    Hello, Sky! 👋

    Congrats on finishing another challenge! After your nice comment, I saw that you added another solution. Everything works good and responds well but take a look at:

    As you can see in your solution scrollX appear, and we don't want that. This is because you position your .icons wrapper with top and left property but hand in hand with position: relative. This is how I'd reccomend you to do it. Add position: relative to your .content-section wrapper. Then to your .icons wrapper add these styles to position it within that .content-section container (Remember that you will need to change the bottom / right value on mobile) (Personally, I wouldn't use relative / absolute to set this icon wrapper. Instead I'd use flex properties to set this but this is another story):

    position: absolute;
    bottom: 0;
    right: 0;
    

    Additionaly, let's add flexbox to this .icons wrapper. display: flex; gap: 10px;. Now there's a part when you want to style your circle border on this icons. Remove all .icon styles, since we'll apply them on anchor tags instead:

    padding: 2%;
    margin: 0 1%;
    border: 1px solid white;
    border-radius: 50%;
    

    Now to your anchor <a> elements with icons add class (it'd be easier to style them). Now what we have to do is set certain width/height to them and align all items center - like this:

    display: flex;
    justify-content: center;
    align-items: center;
    width: 35px;
    height: 35px;
    

    Now, take care about borders on it. To new anchor class add also:

    border: 1px solid white;
    border-radius: 50%;
    text-decoration: none;
    

    Besides that, take a look at:

    • Change the alt attributes for the .responsive-img , .logo-img , as they don't add any extra context for screen reader users. Since your images are decorative your alt text should be provided empty (alt="") so that they can be ignored by assistive technologies.
    • Additionaly you'd have to add some aria-label on anchors with icons to describe it for screen readers users since icons are treated like there is no content within anchors so it won't be announced.

    Good luck with that, have fun coding! 💪

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 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