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

Huddle Single Introductory Section 🎯 [ SEMANTIC HTML - TAILWIND CSS ]

accessibility, tailwind-css
Abdul Khaliq 🚀•72,380
@0xabdulkhaliq
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


👾 Hello, Frontend Mentor Community,

This is my solution for the Huddle Landing Page with Single Introductory Section.

  • It's been the first time using Tailwind CSS along with yarn as package manager 🛠️
  • Used Prettier code formatter to ensure unified code format ⚙️
  • Scored 99.125% on Google Pagespeed Insights! 🤩
  • Solution with 99.9 Percent Accuracy 🎯
  • Layout was built responsive via mobile first workflow approach 📲
  • Had a lots of fun and pain building this challenge ! 🥲

Now for the questions :

  • Regarding, css optimization for production. I tried tailwindcss's --minify for css code reduction. but it ended up with removing the manual style i wrote on input.css
  • But surprisingly the apply directives won't get affected but manual css does
  • At last i used an online css minifier for production, So i want to know why --minify purges manual css on input.css file
  • And, This is for the first time i using Tailwind CSS so apologizing for to many arbitrary values to attaining so called Perfection
  • Finally, Feel free to leave any feedback and help me to improve my solution (or) make the code clean!

.

👨‍🔬 Follow me in my journey to finish all newbie challenges to explore solutions with custom features and tweaks

Ill be happy to hear any feedback and advice !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,720
    @markuslewin
    Posted about 2 years ago

    Tailwind can't detect which classes are being used, because it can't find your HTML file. If you update the content field in tailwind.config.js to include the path of index.html, it should work!

    Is there a reason for the margin-left on the container of the mockup image? I think it looks much better without that declaration.

    Marked as helpful
  • Doston Nabotov•950
    @dostonnabotov
    Posted about 2 years ago

    Hey, there! 👋

    Congrats on completing the challenge. I really liked your attention to details in your HTML and CSS. Also, I do have suggestions as well:

    HTML:

    • It's better use aria-hidden: true on decorative images and icons, making it unreachable for screen readers. You can read more here on MDN Docs
    • Also, setting an arbitrary size for images <img width="709" height="506" > might not be a good idea since they can cause weird overflows on small devices

    CSS:

    • I see that you used fancy link in your attribution section. But, the way you implemented might impact the GPU performance. In other words, it's very costly to use width property when animating things. Also, you might have noticed not smooth, but quite rough animation on hover. I would rather switch to transform or scale properties.

    This code:

    .attribution a::before {
          width: 0%;
    }
    
    .attribution a:hover::before {
          width: 100%;
    }
    

    can be turned into this:

    .attribution a::before {
          transform: scaleX(0);
          transform-origin: < left | right >;
    }
    
    .attribution a:hover::before {
          transform: scaleX(100%);
    }
    

    It might not boost your website performance, but taking care and preventing this issue can help you in the long run.

    Good luck on your coding journey!

    Marked as helpful
  • Francesco Merighi•930
    @francescomerighi1202
    Posted about 2 years ago

    Your solutions is 99.9% perfect, the best i've ever seen, well done!

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

Oops! 😬

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

Log in with GitHub