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

English Dictionary App

react, typescript
Oleksandr•690
@Oleksandr-Berd
A solution to the Dictionary web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


English Dictionary App English Dictionary App is a web application built with React and TypeScript. It utilizes the Free Dictionary API to provide users with word definitions and related information. The app allows users to search for words, view definitions, play audio pronunciations, switch between different fonts and themes, and enjoy a responsive design across various devices.

Features Word Search: Enter a word and retrieve its definitions. Form Validation: Receive a validation message when submitting an empty search form. Audio Pronunciation: Listen to the correct pronunciation of a word if audio is available. Font Customization: Switch between serif, sans-serif, and monospace fonts. Theme Selection: Toggle between light and dark themes for personalized visual styles. Responsive Design: Experience an optimal layout on any screen size. Interactive States: Enjoy hover and focus states for interactive elements. Technologies Used React TypeScript Free Dictionary API CSS HTML Installation and Usage Clone the repository: git clone <repository-url> Navigate to the project directory: cd english-dictionary Install dependencies: npm install Start the development server: npm start Access the app in your browser at: http://localhost:3000 Reflection Building the English Dictionary App was a valuable opportunity to enhance front-end development skills, work with APIs, and practice React and TypeScript. The project provided hands-on experience in handling user input, fetching data, and creating an intuitive user interface. It was an enjoyable challenge that contributed to a deeper understanding of web application development.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Oleksandr'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 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.