🖼️ Update Footer Logo to Match the New Branding

[imuniqueshiv]

Description

The application has already been updated with the new MeetOnMemory branding; however, the footer still displays the old logo. This results in inconsistent branding across the application.

The goal of this issue is to replace the old footer logo with the latest approved logo while maintaining proper sizing, spacing, responsiveness, and visual consistency.

Important: This issue is limited to updating the footer logo only. Do not modify the footer layout, content, or unrelated UI components.

---

Files to Review

client/src/components/Footer.jsx

client/src/assets/

Update any additional asset imports only if required.

---

Tasks

• Replace the old footer logo with the latest approved MeetOnMemory logo.
• Ensure the logo size and alignment remain visually balanced.
• Maintain consistent spacing with surrounding footer elements.
• Verify the logo displays correctly across desktop and mobile devices.
• Ensure the logo looks appropriate in both light and dark themes (if applicable).
• Remove any unused logo assets or imports related to the old branding.

---

Acceptance Criteria

• ✅ Footer displays the latest approved MeetOnMemory logo.
• ✅ Branding is consistent across the application.
• ✅ Logo is properly aligned and responsive.
• ✅ No layout or styling regressions are introduced.
• ✅ No console, lint, or build errors.

---

Before Opening a Pull Request

Run the following commands:

npm run format:check
npm run lint
npx prettier . --check
npm run build

Include Before & After screenshots of the footer in your Pull Request.

---

Difficulty: Good First Issue
Estimated PR Size: Small (≈10–40 LOC)

[revatikadam0607]

\claim

[revatikadam0607]

Description

The application has already been updated with the new MeetOnMemory branding; however, the footer still displays the old logo. This results in inconsistent branding across the application.

The goal of this issue is to replace the old footer logo with the latest approved logo while maintaining proper sizing, spacing, responsiveness, and visual consistency.

Important: This issue is limited to updating the footer logo only. Do not modify the footer layout, content, or unrelated UI components.

Files to Review

client/src/components/Footer.jsx

client/src/assets/

Update any additional asset imports only if required.

Tasks

• Replace the old footer logo with the latest approved MeetOnMemory logo.
• Ensure the logo size and alignment remain visually balanced.
• Maintain consistent spacing with surrounding footer elements.
• Verify the logo displays correctly across desktop and mobile devices.
• Ensure the logo looks appropriate in both light and dark themes (if applicable).
• Remove any unused logo assets or imports related to the old branding.

Acceptance Criteria

• ✅ Footer displays the latest approved MeetOnMemory logo.
• ✅ Branding is consistent across the application.
• ✅ Logo is properly aligned and responsive.
• ✅ No layout or styling regressions are introduced.
• ✅ No console, lint, or build errors.

Before Opening a Pull Request

Run the following commands:

npm run format:check
npm run lint
npx prettier . --check
npm run build
Include Before & After screenshots of the footer in your Pull Request.

Difficulty: Good First Issue Estimated PR Size: Small (≈10–40 LOC)

@imuniqueshiv Hi there! I have worked on a solution for this issue locally, verified the changes, and have it completely ready to go.
Could you please assign this issue to me so that I can open the Pull Request and link it properly? Thank you so much!

[mrunmayeekokitkar]

\claim

[revatikadam0607]

\claim

Hi @mrunmayeekokitkar ! 😊 I just wanted to let you know that I've already completed almost all of the work for this issue. I was only waiting for the maintainer to assign it to me before submitting the PR.

If possible, would you mind picking another issue instead? I'd really appreciate it, since I've already invested a good amount of time into this one. Thank you so much for understanding! 🌸

[imuniqueshiv]

@revatikadam0607 @mrunmayeekokitkar Thank you both for your interest in contributing! ❤️

Since the /claim command wasn't working properly, I'm following a first-come, first-served policy for fairness. As @revatikadam0607 requested the issue first and has already completed most of the work locally, I've assigned this issue to them.

@mrunmayeekokitkar, thank you for understanding. Please feel free to pick another open issue—there are plenty of opportunities to contribute, and I'd love to review more of your work soon.

⭐ If you both find the project helpful, please consider giving the repository a star. Happy contributing!

[revatikadam0607]

@revatikadam0607 @mrunmayeekokitkar Thank you both for your interest in contributing! ❤️

Since the /claim command wasn't working properly, I'm following a first-come, first-served policy for fairness. As @revatikadam0607 requested the issue first and has already completed most of the work locally, I've assigned this issue to them.

@mrunmayeekokitkar, thank you for understanding. Please feel free to pick another open issue—there are plenty of opportunities to contribute, and I'd love to review more of your work soon.

⭐ If you both find the project helpful, please consider giving the repository a star. Happy contributing!

Thank you so much @imuniqueshiv for assigning the issue to me and for handling it fairly. I really appreciate it! 😊
I've submited the PR #60 . Thanks again for your support and for maintaining such a welcoming open-source environment. 🚀