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

Huddle landing page with Sass

sass/scss
IO•710
@i000o
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


What are you most proud of, and what would you do differently next time?

I'm proud of the fact that this page is a bit more populated than the other HTML & CSS only challenges, so it took a bit more breaking down, but I'm happy with how it looks. I did well on the active states, I have an accurate eye for design and I did this quite quickly considering how many decisions there were to make on this one.

I want to be mindful of my Sass nesting this time. Thankfully, on this challenge, I had the opportunity to use branching in Git for the first time to test out a way to improve the nesting in my Sass code. (I was using it too much and in the wrong ways.) This was really useful, although took some time. Learning new git commands always feels good, especially when you have a more conceptual understanding of what they're doing.

What challenges did you encounter, and how did you overcome them?

I had a hard time with the bg-img, again. I'm not comfortable with these yet, although this one took me less wrangling than in challenges prior. Something I'm not clear on is how to stop it from cutting off where <body> ends as I don't put my <footer> with the attribution inside of <body>. Separate from this, on scroll, my bg-img cuts. This has happened before and I don't know how to address it - Help appreciated.

As I said, I made a new branch for the first time to fix the nesting in my Sass. I was using nesting too keenly and not with purpose. It can cause errors in that way, and now I understand more how it impacts my output.css file.

What specific areas of your project would you like help with?
  1. Please help with background-image. It cuts off on scroll. Why?
  2. Are Font Awesome the only way people use social icons? Why do they name their classes fa fa-instagram for instance? How can I refer to the class directly when it has a space in it? I had to use nth-child() to get around this. It was annoying.
  3. I know the Responsiveness can be improved between Tablet - Desktop, but I'm not sure how to go about redesigning the page proportionally to flex down/up nicely. I'd like help with this if anyone has ideas, I'll also look at how other devs responsively designed.
  4. Feedback on Sass as per. Was there anything more I could've used? An @mixin on :active maybe for repeated declarations? I'd like to make the most of it.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on IO's solution.

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.