Added Newsletter-Form

[meghanakn473]

I have added newsletter form in the footer section at the place u have asked me for,
This form helps users to subscribe and be updated with events.

@RamakrushnaBiswal please review and allow merge and assign the level 3, gssoc-extd, hacktoberfest labels
i hope ull conside it

Summary by CodeRabbit

• New Features

  • Introduced a newsletter subscription feature with a new NewsletterForm component.
  • Added a new API route for handling newsletter subscriptions.

• Bug Fixes

  • Corrected a typo in the error handling middleware import.

These updates enhance user interaction with the newsletter service and improve application stability.

[coderabbitai]

Walkthrough

The changes in this pull request involve the addition of a newsletter feature in both the backend and frontend of the application. A new route is introduced in backend/index.js for handling newsletter subscriptions, alongside a correction of a typo in the error handling middleware import. In the frontend, a new NewsletterForm component is created within the Content component, allowing users to submit their email addresses for newsletter subscriptions. This component manages its own state and handles form submissions.

Changes

File Path	Change Summary
backend/index.js	- Added a new route for newsletters: app.use('/api', newsletterRoute);
	- Corrected typo in error middleware import: errrorMiddleware to errorMiddleware.
frontend/src/components/Shared/footer/Content.jsx	- Introduced a new NewsletterForm component for managing email subscriptions and form submissions.

Possibly related PRs

• Newsletter saved to db and a thank you mail is sent to email #174: This PR introduces a new controller function subscribeToNewsletter and a route for handling newsletter subscriptions, which directly relates to the new route added in the main PR for handling newsletters.

Suggested labels

enhancement, level3, gssoc-ext, hacktoberfest accepted

Suggested reviewers

• RamakrushnaBiswal

Poem

🐰 In the footer, a form does bloom,
For newsletters to chase away gloom.
With a click and a cheer,
Emails will steer,
Updates and news will soon zoom! 📬✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b208e66 and ca236ac.

📒 Files selected for processing (1)

• frontend/src/components/Shared/footer/Content.jsx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/src/components/Shared/footer/Content.jsx

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[vercel]

@meghanakn22 is attempting to deploy a commit to the bunty's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Actionable comments posted: 3

🧹 Outside diff range and nitpick comments (1)

backend/index.js (1)

7-7: Typo correction approved with a minor suggestion.

The correction of the typo in the error middleware import is good. It fixes a potential bug in the application.

Consider removing the comment "// Corrected typo" as it might become outdated or unnecessary in the future. The correct spelling itself is sufficient.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8fbf6c1 and b208e66.

📒 Files selected for processing (2)

• backend/index.js (2 hunks)
• frontend/src/components/Shared/footer/Content.jsx (1 hunks)

🧰 Additional context used

🔇 Additional comments (4)

backend/index.js (1)

6-6: LGTM: Newsletter route successfully added.

The addition of the newsletter route aligns with the PR objectives. The import statement and route middleware are correctly implemented, maintaining consistency with other routes in the application.

Also applies to: 22-22

frontend/src/components/Shared/footer/Content.jsx (3)

12-12: LGTM: NewsletterForm added to Content component

The NewsletterForm component has been appropriately added to the Content component's return statement.

---

17-19: LGTM: NewsletterForm component declaration and state management

The NewsletterForm component is correctly declared as a functional component, and useState is properly used for managing email and message states.

---

Line range hint 1-62: Overall assessment: Good implementation with room for improvement

The NewsletterForm component has been successfully added to the Content component, fulfilling the PR objective. The implementation is functional and generally well-structured. However, there are opportunities for improvement in the following areas:

1. Error handling: Enhance the differentiation between network and server errors.
2. Accessibility: Add proper labeling and ARIA attributes to form elements.
3. Responsive design: Reconsider the absolute positioning of the form for better layout across different screen sizes.

These improvements will enhance the user experience, accessibility, and maintainability of the code. Overall, the changes are a good addition to the project, and with the suggested refinements, they will be even more robust and user-friendly.

[meghanakn473]

@RamakrushnaBiswal please review and allow merge

[RamakrushnaBiswal]

@meghanakn473 its not match with the UI and make alignment properly

[RamakrushnaBiswal]

@meghanakn473 also resolve coderabit suggestions

[meghanakn473]

@meghanakn473 its not match with the UI and make alignment properly

What kind of modifications do u want ? Can u please describe @RamakrushnaBiswal

[RamakrushnaBiswal]

@meghanakn473 remove the background

make something like this and add it here

[meghanakn473]

@RamakrushnaBiswal please check now