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

Alternative huddle landing page

accessibility, tailwind-css
rashed-mia•30
@rashed-mia
A solution to the Huddle landing page with curved sections challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?
  • complete with Tailwind CSS
  • making layout flex and grid
  • learn positioning
What challenges did you encounter, and how did you overcome them?
  • I have faced a challenge in the footer
  • It's hard to make an absolute positioning
What specific areas of your project would you like help with?
  • It's time to go footer
  • Header is an amazing part
  • and a pop-up card in the footer
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Daniel Ayeni•1,240
    @Dannimations
    Posted 4 months ago

    Well, I think you submitted the project in the wrong place, but I understand what you were trying to do.

    For starters, you can try changing the appearance of the buttons and links when they're being hovered over, to give some sense of user functionality.

    You can achieve something like that using the 'hover' state attribute in the css

    button:hover{ }

    and then put the properties of the hover in the curly braces.

    Then for the footer, I had issues with it before, but I think you nailed it. Just use a basic flexbox for the layout, and if the div's are put in the right place, everything kinda falls into place automatically.

    Hope this helps:)

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