This week’s episode talks about whether you even need to have a backend for your website.
If you haven’t listened to our episode on this topic, please take some time to do so.
Ultimately this is a decision that you need to figure out for yourself, we can’t give you the answer to this question. However, we can guide you in your decision.
Does you website need any functionality? By functionality, I don’t mean some animations, navbar, or anything like that. What I am referring to is anything that deals with a database, email sending, and the like. If the website requires a contact system that would allow the user to contact the website owner then you would need a backend. If you are storing any data, you could store it on a flat file on your front end, but that probably isn’t the best idea. It’s not very secure for one, for two, you probably need a backend. If you are storing any user information, you need a backend. Don’t store that on your front end.
If you don’t believe me, check the development tools in your browser. You can view file data stored in your front end project. So please, for the sake of your users, and your legal assets, please don’t store user data there.
If all you need is to store some various information with no functionality, then you don’t need a backend.
We hope this helps, but please take a listen to the podcast episode if you haven’t already. We talk much more in depth there.