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

Responsive app built with React/React-Router/Material UI

react, react-router, material-ui
Matt West•440
@matt-o-west
A solution to the Planets fact site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Deployment and state management gave me some headaches in this one. I still have a bug I need to fix where if you refresh the page, the GET request fails even though the route looks fine. Any ideas how to resolve this?

I utilized React-Router and any best practices related to this would be appreciated, I don't know if I implemented it in the optimal way. That said, I think I am getting much better now that I am comfortable building in React to the point where I can pull in UI libraries. Hopefully, it's an upward trajectory from here!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,760
    @markuslewin
    Posted almost 3 years ago

    This comment was deleted almost 3 years ago

    Marked as helpful
  • Chamu•13,860
    @ChamuMutezva
    Posted almost 3 years ago

    Hi Matt

    So far so good on your project. You managed to pull the data from the json file, but what you really need to work on is your styling as your page is not responsive. Practice styling on a project that is of a lower level than this one. A site should generally be able to be viewed on any device smoothly

    • all img should have a alt property and an img is a self closing element . <img src="./image.jpg" alt="" />
    • interactive elements such as buttons and anchor element should have readable text that is available to assistive technology users.
    • see also the feedback response
    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

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

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