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

WordWise: A Responsive Dictionary App Built with Next.js and Tailwind

P
Skyz Walkerβ€’1,215
@Skyz03
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?

Reflecting on this project, I take pride in several key achievements. Firstly, I significantly improved the design system, particularly in defining the styles for titles and body elements. This clarity not only enhances the visual appeal but also ensures a consistent user experience throughout the application. 🌟 Additionally, I implemented a direct Google search feature for synonyms, which adds immediate value and functionality for users looking to explore word meanings further. πŸ”

While I am proud of these advancements, there are aspects I would approach differently in future projects. For instance, I would focus on enhancing accessibility features to ensure that all users can navigate and utilize the app effectively. β™Ώ

Furthermore, I would consider integrating more dynamic content options, such as user-generated word lists or personalized vocabulary tracking, to foster greater engagement. πŸ“š Lastly, refining my use of Tailwind CSS utilities could streamline my styling process even further, ensuring that my code remains clean and maintainable as the project scales. πŸš€

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

During the development of my dictionary web app, I encountered several challenges that tested my problem-solving skills. One significant challenge was mapping the proper information into the UI in a structured format. Ensuring that data was displayed clearly and intuitively required careful planning and iteration. To overcome this, I focused on creating a clear layout and utilized components effectively to organize the information, allowing for a more user-friendly experience. πŸ› οΈ

Another challenge was implementing Dark Mode. The complexity arose from the need to manually adjust each element to ensure it looked good in both light and dark themes. πŸŒ— This process was time-consuming and required meticulous attention to detail. To address this, I researched best practices for theming in Tailwind CSS and began implementing a consistent approach across components. Moving forward, I plan to explore Tailwind's built-in Dark Mode features more thoroughly, which could streamline this process and make future implementations more efficient. βš™οΈ

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

I would appreciate help in a few specific areas of my project. Firstly, I’m looking for guidance on optimizing the mapping of information within the UI to ensure that data is presented in the most effective and user-friendly way possible. Any insights or best practices for structuring data visualization would be incredibly helpful! πŸ“Š

Additionally, I would like assistance with the implementation of Dark Mode. Since I found it quite complex to manually adjust each element, any advice on leveraging Tailwind CSS’s built-in Dark Mode features or resources on best practices for theming would be invaluable. 🌈

Overall, any help or suggestions in these areas would greatly enhance my project and contribute to its success! Thank you! 😊✨ Feel free to adjust any emojis or phrases to better match your style!

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 Skyz Walker'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.