This is not a Issue - More Info
Hi,
Thank you for this repo and this article (https://joshuastuebner.com/blog/backend/nuxt_static.html). You have done really nice here.
I am currently working on a Recipe website for one my friend also it is more of learning for me. I saw you also have worked on a recipe website. Do you mind sharing the link to it?
I need some thoughts from you (You have all the rights to ignore this message if you do not want to answer me).
Since this project does not have any monetary benefit most of my steps will concentrate on free resources. I will explain my project in to two parts and this is the current way i am taking it:
- To Add/Edit/Delete Recipes:
-
I will use firestore as recipes data backend -
I will use google storage to store recipe images -
I will run nuxt on Universal mode on Amazon AWS using micro instance which is free for a year.{I would like to avoid this soon)
- Application open for users to read recieps:
-
This will be Nuxt application Difinitely SEO friendly -
This I would like to have as a pure Static website as I do not want call to go to Firestore api. -
Based on your approach below cycle is suitable - a. Have a json file which stores recipes , which should get generated once in a day or after each add/edit of recipes.
- b. My Nuxt app should use this json file to read the recipes.
- c. The files should be stored on website like netlify should be refreshed on a daily basis.
I may not be right in putting my steps or the wordings used. But your input will assist me in a big way.
So the basic requirement will be to have a website which will have 5000 visitors daily(This is not true as of now :) ) There will be daily add/update of new recipes which will have images. There will be around 500 recipes to start off might increase over the time.
So what will be your advise to go ahead with the this small project.
Once again thank you very much for your help.