Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

responsive react web app

react, vite, sass/scss
Jamil Aliyev•240
@LieutenantCobretti1998
A solution to the Dictionary web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

This my first self-made react app in which I learned so much about react working under the hood, especially how react use re-render techniques. I understood how use much more efficient react re-render avoid techniques such as callback and memo methods. With the help of react I managed to create a simple web app in much less time than with using vanilla JS. I also went beyond the original tasks for this challenge and add the option of saving words in local storage and extract the saved words with their pronunciation, explanation, and type to the excel file via sheet.js. In order to check your saved words you can press to the book svg on top left bottom of the page and thats all 😁

In the future I want to make website more beautiful with using smooth animations on it😍😁.

Please, give me a star in GitHub, if you really like my website. Thanks in advance❤️😁

What challenges did you encounter, and how did you overcome them?

The biggest challenge for me was making react not to re-render all components due to each change. Now I understood, how it was important to create a plan for react app and its tree before starting to code itself🥲

What specific areas of your project would you like help with?

Animations! Maybe someone have some ideas or library suggestions (except anime.js, because I already know it😅) for making my website much more beautiful:)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lejla•130
    @LejNur
    Posted 12 months ago

    Great job! I really like your solution. I myself am starting challenges in react and I know how react can confuse you at the beginning especially with re-rendering.. Keep up the good work!

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.

Oops! 😬

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

Log in with GitHub