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

Landing Page built with SCSS & Bulma (CSS Framework)

Bonrey•1,130
@Bonrey
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, folks! 🎉

Once again, I decided to try out something new, and this time my choice was another CSS framework — Bulma.

At first, this tool seemed very useful to me. There was nothing complex and it helped me add basic styles in no time. However, as I went on with the project, I needed my site to be more responsive and some of the predefined classes didn't suit my needs. That's why I ended up writing lots of @media queries and other styles.

Anyway, I enjoyed working with Bulma way more than with Bootstrap, especially, when it came to responsiveness. I think it has something to do with its simplicity. However, if someone asked me whether I'd prefer writing my own styles or using one of the CSS frameworks mentioned above, I'd most likely go for the former.

I'll probably try out a couple more CSS frameworks before making up my mind, though 😁

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hey, Bonrey! 👋

    Just wanted to drop into say well done, once again, on another challenge! 👍 Everything's looking pretty on point! 👌 (I like the custom favicons you've been adding to your solutions, BTW.) 😀

    I also think it's interesting to hear your thoughts on CSS frameworks (since I mentioned I haven't really tried them out very much, yet) compared to good ol` regular CSS. If you're up for it, keep on trying new things (as you mentioned), and I'll be looking forward to hearing about your experiences with them! 😅

    As always, keep coding (and happy coding, too)! 😁

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

    Another great 👌 project from you @Bonrey

    You worked quite a lot on this project as it seems...

    I would like you say something, may I?

    • You are the second one I saw using placeholder classes, I am really happy..! You are quite interested in SCSS
    • Why not using a mixin for all those media queries... DRY should be followed, no?
    // conversion from pixel to rem
    @function rem($var) {
        $result : $var / 16;
        @return $result * 1rem
    };
    
    // responsiveness 
    $breakPoints : (
        'extraSmall' : rem(320),
        'small' : rem(375),
        'large' : rem(768),
        'tab' : rem(1024),
    );
    
    @mixin responsive($size) {
        $breakPoint : map-get($breakPoints, $size);
    
        @media screen and (max-width : $breakPoint){
            @content
        }
    }
    
    • I would suggest learn dart-sass and use scss modules and stop using import as the higher developer are suggesting because import will be deprecated see this article

    • I see people using css framework but I don't know why but it doesn't feel important to me...any suggestions?

    Hope these helps you and happy 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 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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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