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

Responsive Website using ReactJS, styled-components, and React-Router

react, react-router, styled-components
Achmad Muqorrobin•270
@Muqorrobin22
A solution to the Designo multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My solutions in this multipage website using Styled-components , ReactJs and React router. also i bring the animations on Router with react-transition-group and using react-reveal

i spend about 3 days ( obviously not working a day long , oh very exaggeration😁 ) to build this amazing design designo website .

Any Feedback and comments are Welcome!

Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•2,010
    @AlexKMarshall
    Posted over 3 years ago

    This is a very big project. Good effort for completing it.

    Be careful with your html structure. You need to use heading levels correctly. There should only be one h1 per page, and all other headings should follow in the logical order - think of them like a table of contents. Your pages need a main element for the principal content of each page too.

    Make sure that you consider accessibility. You need to include :focus-visible styles for all interactive elements. Most of the links on the pages are unusable with a keyboard as you can't tell which are selected. You also have a lot of moving animations - these must be switched off if the user has prefers-reduced-motion set, not doing so can cause significant problems for those users.

    The animations are also causing problems with the text. Because each letter is wrapped in its own span, the text breaks at weird points in the middle of words when it moves to the next line.

    Make sure that you check your design at all screen-sizes. You have horizontal scroll-bars that appear at above approximately 780px screen-width, and your footer grid content doesn't line up.

    On the contact page your form elements are all missing labels. Make sure to use the correct type for the inputs as well. The telephone number should have type="tel". Type="number" is more suitable for something like a quantity field. That way the user will get the correct keyboard to use on mobile, and you won't get things like number input spinners on desktop which aren't appropriate for a telephone number. The form contact errors for missing fields should only show when you try and submit the form. Currently they show as soon as you enter the page.

    Be careful when using react router and Netlify. Your links all work when you enter the site by the homepage, but if you try to bookmark the 'contact' page, for example, you will get a 404 error when trying to visit it. There are some extra settings you need to set up on Netlify to make this work properly.

    Make sure you use the correct size images. It seems like on desktop you are serving images that are too small, and they're getting scaled up, so they look blurry. This is particularly noticeable on the about us page. You need to make sure you serve the correct size image for the device the user is on. Also, make sure you have correct alt text. <img src="/static/media/image-about-hero.cd9299f7344ca7b76793.jpg" alt="/static/media/image-about-hero.cd9299f7344ca7b76793.jpg"> is a meaningless value. https://supercooldesign.co.uk/blog/how-to-write-good-alt-text

    I apologise if this seems like I'm being quite picky and raising a lot of issues with the site (that's my background in QA testing coming through). But this is a big site, and there is a lot of things to do on it. I would suggest it would be worth trying a few of the smaller challenges and really make sure that you're nailing the fundamentals correctly.

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.

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