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

Custom CSS Library, used Flexbox and utility classes to style elements

node, react, sass/scss, vite
P
Arsalan2078•70
@Arsalan2078
A solution to the Blog preview card 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 am most proud of being able to use my custom css library. This will very significantly quicken styling process and reduce setup.

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

I encountered issues with css specificity, speficially with my padding classes which were generated automatically.


    Learning

p-xs-100 is responsible for mobile screen size padding on all sides, while pt-xs-50 and pb-xs-50 added padding on top and bottom respectively. The latter two didn't override paddings set by p-xs-100 class, which was generated after the two.

I addressed the issue by creating two scss loops:

  • First generates universal margins and paddings
  • Second generates margins and paddings on one side at a time
What specific areas of your project would you like help with?

I am not particularily happy with my typography, and there are definitely more techniques and tips I could use to improve upon scss.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ErwiniaDev•100
    @ErwiniaDev
    Posted 8 months ago

    Hi, there, First of all, I'm sorry I'm such a beginner so my feedback won't necessarily be the best...

    Congrats for your project, it's near to the model!

    The only detail I found was the border-radius of the card (the model's is smaller than yours, 10px if I'm not being silly). However, I did find your border-radius: 0.625rem in your style.css (line 2675) but only for the image. It's 1.75rem (line 2671) for the card.

    I hope my feedback helps you in spite of everything. All the best!

    Marked as helpful
  • xNyfPtx•1,260
    @xNyfPtx
    Posted 8 months ago

    bro your library already exists. check out tailwindcss

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