New update! I've successfully used Next JS API routes to create a serverless function that handles getting state resources from an Airtable Database instead of serving some local JSON. I left the option to use the local JSON however in case others wish to contribute to other parts of the app and don't need access to Airtable. It was also super nice to see tests pass and build not fail from the GitHub actions checks which are also officially added and updated. An awesome new thing I learned while working on this.
Here is my next major goal: Allow for user-submitted resources. Setting up Airtable was a part of this but here is what I plan to do in the next couple versions of this leading up to my v1 for submission to the hackathon:
- Make an API route for creating resources - by default they will be in an unapproved state
- Use Tailwind UI to make things look nicer and build a pleasant-looking form
- Integrate Zapier so I can get an email notification whenever someone submits on the form and my Airtable database gets updated
- Create a workflow for myself that lets me quickly look at the email notifications with the resource and approve them if they are appropriate.
Something I've noticed so far with this that I wish I had done with earlier projects: even unfinished it is useable. The first update I put out only had resources for two states and was a very small and simple UI. It still worked and helped people in those states. Now it holds much more and I've already gotten feedback that someone was able to use it to find a resource in their local state. This alone makes this entire project worth it.
To see current progress check it out below! Hoping to have a domain name as well once I do submit.
Top comments (0)