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

Dictionary App made w/ Remix, TS, Postgres, Tailwind

react, remix, tailwind-css, typescript, postgres
Matt West•440
@matt-o-west
A solution to the Dictionary web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! This started as a simple challenge, but as I moved through it I decided to add features, got ideas and ran with them. The app uses the merriam webster api and parses the returned data at dynamic word routes with SSR'ed pages. Search results are fetched client side, parsed, and output in an autocomplete result dropdown in real time. Handrolled authentication allows for user profiles and saved words. Words are voted on and stored in a serverless postgresql db. The app uses Remix's loaders and actions to deliver and return data. Google sign-in is also available to authenticate.

First: if you see a bug please send to me!

There were some very frustrating parts of this app, but I feel like I grew a lot from it. There are a couple janky workarounds for things I couldn't completely figure out, like syncing localStorage and database values (which I had a fix for at first, but then came back to with it not working, more below), I will hopefully be able to go back and update them. Surprisingly, the auth was one of the most painless aspects, while styling and generally working with the voting data/schema was difficult at tunes.

My real take away from this project is that I desperately need to start writing tests. Because I didn't go into the project thinking it would be this comprehensive, I just never wrote them and it definitely made life more difficult - I kept coming back and finding bugs or items I had done or fixed, and they had reverted! Maybe I need to work on my git workflow as well to avoid that.

I tried to improve my semantic html, but am unsure if it's really up to par, if you have any tips or pointers let me know. Or, if you have recommendations for improving anything I did sub-optimally, please let me know.

If you like the app and have words of encouragement, please share them!

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 Matt West'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

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.