Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Huddle with scss and a lot of flexbox

accessibility, sass/scss, parcel
Fluffy Kas•7,675
@FluffyKas
A solution to the Huddle landing page with alternating feature blocks challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys,

I wanted to practice some CSS with this challenge as I was focusing a lot more on Javascript recently and felt like I was getting a bit rusty ^^ I'd like to get some feedback, especially on the semantic side of things, if there's any way to improve what I did, I'd love to know! If anyone could suggest some animations for the hero section of the page, I'd appreciate that too! I don't have a lot of experience with animations and I don't want to go overboard with them, but without any that section seems a bit... plain? >.>

Any feedback, good or bad, is greatly appreciated! Have a lovely day!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Duyen Nguyen•950
    @Duyen-codes
    Posted over 3 years ago

    Your solution looks great! I'm planning to do this challenge and coming across your profile. I'll definitely go back to have a look at your solution again to compare with mine and learn from yours. May I ask how long have you been learning web dev and how have you learned so well? I have quite ok knowledge with html css but still struggle a lot with JS. I've seen that you have completed the space landing page challenge, which is my challenge goal but I am not that good with JS that i can't do that yet. Happy to connect with you!

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