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

Huddle Landing page with Tailwind Css

tailwind-css
P
Judge Micko S. Silvestre•415
@mickoymouse
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


Another one for today!

I had fun doing this one. As usual, I set my expectation on how long I think it would take me to do this and my expectations are more or less accurate. That being said, I am definitely rusty and in need of many more challenges to get back on groove!

Specific part I would like to get feedback here is the socials part. I was wondering what other approach or what the best approach is to put it on the lower right with the rest of the items still dead center. My approach was using absolute positioning but I feel it's a bit scuffed. I can't shake the feeling that there is definitely a better approach.

That being said, I am excited to see how my fellow developers implemented their solution!

As usual, feedback and constructive criticism are definitely welcome and appreciated. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted over 1 year ago

    Hello,

    Very neat solution! Kate has already answered your question, so I'm just gonna mention something else: your social links would be better off semantically as a <ul> with list items. Each image could be wrapped in a link with the appropriate aria-label to describe where they are leading to (for people who don't rely on visuals, but use screen readers for example). Everything else seems great, well done!

    Marked as helpful
  • Kate Dames•250
    @funficient
    Posted over 1 year ago

    Hey! Nice solution!

    I'm not sure if it's best practice, but the way I handled the social icons is by sizing the body as 100vh:

    body {
      background-color: var(--color-primary-voilet);
      background-image: url(assets/bg-desktop.svg);
      background-size: cover;
      background-repeat: no-repeat;
      width: auto;
      display: flex;
      flex-direction: column;
      min-height: 100vh;
    }
    

    The footer element which contains the social icons is then simply positioned at the end of the box which is 100vh.:

    .footer {
      display: flex;
      justify-content:flex-end;
    }
    

    Hope that helps! Kate

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