Daniel -
1. The database is run on Render, which is connected to the backend folder on GitHub on the main branch. When you edit the backend, make sure that Render is deployed with the latest updates.
2. The products might take a minute to load due to Render, which hosts the backend, taking a while to start up after inactivity. You can check if it is loading or if there was an error in the console. In an actual store page, you would pay to have the server run constantly, regardless of activity.
3. For the sake of making this program easier to work with and evaluate, I made the .env public. If you want to actual make it secure, you'll need to use MongoDB to replace the exposed secret keys with new ones and update the Render environment variables new data on Render. You should also add it to the .gitignore
4. The admin pages aren't meant to be accessible by the public, so there aren't any links to them. To access them, you need to type in the URL manually. Also, they are given ordinary names so that they are easier to view, but for an actual site, you should edit the file names and references so that they aren't something a regular user could find, even if they would still need a username and password. Currently, you just change the last section of the URL with the .html to AdminLogin.html. You can't go to the Admin.html directly since you need to log in first.
5. Admin accounts are created manually on the database. Right now, the username is test123@gmail.com and the password is 123456