Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Dictionary web app Using Reactjs

react, sass/scss, vite
P
Ahmed Lemssiah•510
@Arteque
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 is my first project using React.

I think the framework choice was pretty bad. The idea to start a complicated challenge using a framework I'm just starting to learn made it way more challenging, I think. (This is why it took a week for the development and the code refactoring).

I'm happy that I could finish my first React project. I'm immersed in it now, and I've learned so much in this week. Concepts like Hooks, useState, useEffect, and getContext are just mind-blowing, and at the same time, the logic behind them makes sense to me because I was on the edge every time due to component props scope, for example. And I needed a solution to get the data to the App level...

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

The difficulty lies in the fact that React itself can be quite tricky when it comes to managing the app's state and component scope. Checking the local storage proved to be particularly challenging. React's paradigm of unidirectional data flow and component encapsulation necessitated careful consideration of how and where to access and update local storage within the component lifecycle. This required a deep understanding of React's state management mechanisms and the proper utilization of lifecycle methods to ensure data persistence across sessions.

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

The doubt I have is about the structure of the code, the best practices perhaps, and the pitfalls in projects like this one.

I added some features like word autocompletion when the user searches for words... I don't know if it's a good thing or perhaps if there are some ideas on how I can do it better.

All along the way, I was thinking about user experience and how I can reach the level of online apps. Things like keyboard navigation or mouse wheel navigation for the suggested words, for example, could be a nice idea to implement.

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 Ahmed Lemssiah'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 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.