-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat:Newsletter section for engaging with users and collecting their emails #24
Comments
please @Adeesh-bode assign me to this issue under gssoc and please add the labels of GSSOC'24 and the label of appropriate level (like level 1, 2 or 3) on this issue. |
Go ahead @Adeesh-bode |
ok |
hey subhadeep , just a little discussion . Your project doesn't have proper backend as I can see in contact page, just data is collected but not stored. So for now I will create frontend for newsletter and make backend endpoints so that whenever backend database is used one can stored newsletter subscribers email. Will it be ok , to have newsletter frontend as you did for contact form in contact page |
I would be happy to raise backend - mongodb as database by raising another issue , after frontend of newsletter is done. Let me know your opinion on it!! |
???? |
@Adeesh-bode first of all we do have a backend ... (proper one)... i dont want to implement newsletter section. In contact section, someone has already used formspree... but i am not implementing that for now ... first a bit of ui and main pinned issues are to be solved then these. Thank you |
Hello @Adeesh-bode! Your issue #24 has been closed. Thank you for your contribution! |
The issue involves creating a newsletter section on a website or application to engage with users and collect their email addresses. This feature aims to facilitate communication with users, keep them informed about updates or promotions, and potentially increase user retention and interaction. The implementation would typically include designing the user interface for the newsletter signup, integrating it with the backend systems, and ensuring compliance with data protection regulations.
The text was updated successfully, but these errors were encountered: