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

Planet facts site using React/Next.js

next, react, sass/scss
Nick Carlisi•180
@nickcarlisi
A solution to the Planets fact site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi all,

This is my first submission using React/Next.js. All of my other submissions have been "vanilla" html, css, javascript. I feel like I could definitely clean up my code and make it a little more efficient. I feel like it's a little repetitive. I had some issues "sticking the landing" on this one. I feel like the last 10-15% took a similar amount of time as the first 80-85%.

A few issues/areas for improvement

  • I feel like the templated feel of this site (each planet having the same page just with different content) means I could basically loop over the data.json and create a page for each entry, but I'm not sure how to do that. So, instead I manually made a page for each planet. I also feel like I had to pass in a lot of props. I ended passing 10 props into one component. I'm sure there's a cleaner way to do this.

  • I feel like the imagery takes longer to load than it should, especially the zoomed in view of the planet's surface. Whenever I click on the button that shows that view, it takes a good second or 2 before it shows up. Not sure why because these images are so small.

  • I kind of cheated and for the home/index page, I just basically copied the same exact code for the Earth page instead of re-directing the home page to the Earth page. Not sure how to do that.

  • I'm sure there's plenty of more room for improvement. Suggestions/tips are welcome, as always!

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 Nick Carlisi'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 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.