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

FEM - Planet Facts Challenge - build with scss/webpack and JavaScript

cube-css, webpack, sass/scss
Matthias•630
@astragenius
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

Here is my Solution for the "Planet Facts Challenge”

In this Challenge, I used ‘webpack’ for the First time and other tools like

  • PostCSS
  • ESlint
  • Prettier
  • SASS
  • and appropriate loader to load the self-hosted Fonts and images.

The data for the content of each Planet Page gets extracted from the “data.json” with JavaScript. An put on the right place with JavaScript DOM methods.


I used for the First time two CSS- animation library’s

anime.js - to animate the hamburger menu button

Animate.css - to animate the transition between Planet Images and relevant text content.

Plain CSS - to animate the mobile menu itself.

I used two libraries to gain some experience in both systems


I tested the layout for mobile/tablets and Desktop and i tried to keep up with the figma design template as best as possible.

Maybe some of you can give me some feedback 🙂

Does load the text and images correctly on each page?

Does the animation work correctly on each page?

Are some layout issues on your Device?

Or maybe some of you have suggestions for Best Practise etc 🙂

Let me know! 🙂

I hope for your constructive feedback :) Thanks in advance.

Wish you a good day/week :D

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 Matthias'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 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.