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

My first fully responsive landing page, using Dart SASS.

Bonrey•1,130
@Bonrey
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


Hello, everyone! 😃

I decided to take a short break from CSS frameworks and deepen my SASS knowledge a little. And this challenge was a perfect opportunity to do that! I focused only on Dart SASS. It is a specific implementation of SASS that gets all the bells and whistles first. ✨

In brief, here is the list of Dart SASS tools I used for this challenge:

  • variables, mixins, placeholders;
  • built-in modules, such as sass:color and sass:map;
  • @use, @forward keywords instead of @import, which is getting deprecated.

As regards the challenge itself, it was pretty fun. I got a kick out of positioning the curved parts. 😄 And resizing images depending on the screen width was quite enjoyable, too! Finally, it's worth mentioning that I used Font Awesome icons for social media.

As usual, any feedback is very welcome! Probably the only question I have is this: should I avoid extra media queries, or is it okay to use as many as I need?

P.S. I went with the default form validation this time simply because I didn't want to clutter my project with an extra js file. 😏

P.P.S. You can also check out the README.md file on my github page for extra links.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    Hello 👋 @Bonrey

    Very nice work 👍 man..!

    For your answer,

    Learn fluid typography... It will let you use media queries only a few time when changing the layout and that's it..!

    Hope it helps and happy coding..!

  • tediko•6,700
    @tediko
    Posted about 4 years ago

    Hello, Bonrey! 👋

    Well done! Your solution responds well and everything looks good. I can suggest small details like:

    • Since your logo have an anchor tag your alternative text isn't descriptive. Try to change it to 'Huddle home page' or something like that maybe.
    • You disabled outline property for your buttons and anchors. This is wrong from accessibility point of view. Keyboard users can't tell where they are on your page while navigating. Add some :focus to these elements.

    Good luck with that, have fun coding! 💪

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