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

Planets fact site w/ React and SCSS

react, react-router, sass/scss, motion
kristi•130
@kristiingco
A solution to the Planets fact site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, Frontend Mentor community! I would love to gain feedback for this specific project.

I have the following questions:

  • How would one best structure their components? What is the best way to be able to know what components to construct?

  • What are best practices for clean CSS/SCSS code?

  • Are there any pros and cons to other CSS preprocessors?

  • If you could do this project with a React framework (such as Next.js, Gatsby, etc) , what would you choose?

Thank you so much! This project was a blast to do.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • jemeneradev•580
    @jemeneradev
    Posted over 3 years ago

    Personally, I find css preprocessor quite useful. With scss, for example, you can nest css definitions. That makes things logical and neat. You can also have modules and mixins that act a type of style inheritance, so you don't have to repeat common styles. Not to mention loops in css.

    For clean css, you'll just have to look at different approaches. For instance, nowadays, tailwind css is all the rave. I tend to stay away from that because it makes the markup too cluttered. You could also checkout bem (http://getbem.com/introduction/).

    As far as I know, gatsby is content management system, so between the two, I would opt for nextjs.

    Regarding component structure. One rule I follow is, if I find myself repeating code, more than likely it can be group logically.

    Marked as helpful

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