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

using React framework, style by sass, route by react router

react, react-router, sass/scss
Thanh Vu•100
@Hatter-s
A solution to the REST Countries API with color theme switcher challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • When build my app to netlify I have some trouble when reload detail page have issue 404 page not found, if you know why it happen please dm me.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Laerice Dessouassi•450
    @dinadess
    Posted over 2 years ago

    Hi @Thanh!

    Your dropdown menu looks great!

    But while going through the homepage, I noticed I could not access it using the keyboard. That can be an issue for user's who navigate websites using keyboard navigation. Also, in light mode, the options are unreadable when hovering them (dark text on dark background).

    Concerning your 404 error, I encountered the same issue with my Vue App and the solution was to create a _redirects file in the public folder.

    You can find more information here or here.

    Ciao :)

    PS: How did you build the dropdown menu?

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub