newsletter frontend and backend done : #542 done #550
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I think we had a component for mails, you can use that instead of writing separate code for mails. And there are some merge conflicts |
|
@Luson045 sir i have solved the merge conflict. Secondly, i have create other api because keep everything separate is a good thing it enhance code readability and this mail component has some separate body so i think it will be a good thing to keep it separately. Also mentioning again the newsletter page is only allowed for admin role so you have to set your isAdmin to true in mongodb database for that emailid. |
|
also your footer is not looking with that background color and the footer section component is not visible so if you want to change it so i can work on it. |
|
@VinayLodhi1712 okay. A lot of people are working on the footer issue, so I guess it's not needed as of now.. Instead you can work on this issue |
newsletter frontend and backend done : #542 done
So this is the video first of all -
There is some network lag so website is loading slowly, so not mind that
20241025173843.mp4
So you have to keep mind this things -
for newsletter option visible in footer is only visible to the admin. Because i think you don't want that everyone can send the newsletter to the user.
you dont have any admin option so you have to set mongodb isAdmin value to true. See this image-
this is newsletter schema for storing newsletter subscribing mail -
And you need to setup the nodemailer email id and password for sending the emails to the user for that you need smtp mail and password so which you can find its information and store in .env file -
Frontend is decent I think but i have work a lot in this from creating admin middleware to storing admin value and then admin context in frontend and then frontend for newsletter and apis in backend for it. So i have more focused on backend part . If you want any information then i can help you.