docs: fix broken YouTube badge and update link

[hamzanazir27]

While checking the Template-Repo, I noticed that the YouTube badge was broken and not displaying correctly

---

now fixed

---

…Tube badge and update to official channel

Commented out the todo project logo image and updated the YouTube badge.

Addressed Issues:

Fixes #(issue number)

Screenshots/Recordings:

Additional Notes:

Checklist

• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

Summary by CodeRabbit

• Documentation
  • Disabled the project logo image in the README header, replacing it with a commented placeholder to remove the visible logo.
  • Replaced the existing YouTube badge with a simplified, fixed Subscribe badge image for a cleaner header appearance.
  • These changes adjust header visuals and links without altering other documentation content.

[coderabbitai]

Walkthrough

This PR updates README.md by commenting out the todo-project-logo tag in the header and swapping the YouTube badge to a simplified, fixed Subscribe badge image URL.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Commented out the header todo-project-logo image tag; replaced the YouTube badge markup with a simplified fixed Subscribe badge image URL.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Feat/add youtube link #77: Modifies the README YouTube badge image URL and markup, directly related to the badge change here.

Suggested labels

Documentation

Poem

🐰 I hop through lines of README light,

A logo tucked away from sight,
The YouTube badge now trimmed and neat,
Small hops make docs feel whole and sweet. 🥕

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: fixing a broken YouTube badge and updating its link in the README documentation.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kpj2006]

@CodeRabbit review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 44-45: Update the img tag's alt attribute to use the brand-correct
capitalization by changing alt="Youtube Badge" to alt="YouTube Badge" in the
<a>…<img> block (the anchor linking to https://www.youtube.com/@AOSSIE-Org
containing the shields.io badge image) so the alt text matches YouTube's
official capitalization.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 45-46: The YouTube badge currently uses a hardcoded count and
identical label/message color; update the img src in the <img> tag to use
shields.io's dynamic YouTube subscribers endpoint
(/youtube/channel/subscribers/<CHANNEL_ID>) replacing the static
"subscribers-73-FF0000" segment with "youtube/channel/subscribers/<CHANNEL_ID>"
and set a contrasting labelColor (e.g., labelColor=ffffff or label="Subscribe")
so the left label is readable, or alternatively revert the <img> to the previous
static "Subscribe" CTA badge if you prefer a non-dynamic, never-stale badge.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Two issues with the new YouTube badge: hardcoded stale count and invisible label contrast.

1. Hardcoded subscriber count will go stale. The static value 73 in subscribers-73-FF0000 is frozen at the time of commit. Shields.io supports a native YouTube Channel Subscribers badge that pulls live data — consider switching to that instead.

2. labelColor=FF0000 matches the badge color, eliminating contrast. Both the label section (left, labelColor) and the message section (right, badge color) are FF0000, so the whole badge renders as a uniform red block with no visual separator between "subscribers" and "73".

If a live subscriber count is desired, the shields.io YouTube Channel Subscribers badge (/youtube/channel/subscribers/<CHANNEL_ID>) provides a dynamic count without requiring a hardcoded value.

If a static CTA is preferred (simpler and never goes stale), reverting to the previous "Subscribe" badge is a better choice:

🛠️ Option A — Dynamic subscriber badge (preferred)

-  <img src="https://img.shields.io/badge/subscribers-73-FF0000?style=flat&logo=youtube&logoColor=white&labelColor=FF0000" alt="YouTube Badge">
+  <img src="https://img.shields.io/youtube/channel/subscribers/<CHANNEL_ID>?style=flat&logo=youtube&logoColor=white&label=Subscribe&color=FF0000" alt="YouTube Badge">

Replace <CHANNEL_ID> with the AOSSIE-Org YouTube channel ID.

🛠️ Option B — Static Subscribe CTA (no stale data)

-  <img src="https://img.shields.io/badge/subscribers-73-FF0000?style=flat&logo=youtube&logoColor=white&labelColor=FF0000" alt="YouTube Badge">
+  <img src="https://img.shields.io/badge/YouTube-Subscribe-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube Badge">

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	<img src="https://img.shields.io/badge/subscribers-73-FF0000?style=flat&logo=youtube&logoColor=white&labelColor=FF0000" alt="YouTube Badge">
	</a>
	<img src="https://img.shields.io/badge/YouTube-Subscribe-FF0000?style=flat&logo=youtube&logoColor=white" alt="YouTube Badge">
	</a>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 45 - 46, The YouTube badge currently uses a hardcoded
count and identical label/message color; update the img src in the <img> tag to
use shields.io's dynamic YouTube subscribers endpoint
(/youtube/channel/subscribers/<CHANNEL_ID>) replacing the static
"subscribers-73-FF0000" segment with "youtube/channel/subscribers/<CHANNEL_ID>"
and set a contrasting labelColor (e.g., labelColor=ffffff or label="Subscribe")
so the left label is readable, or alternatively revert the <img> to the previous
static "Subscribe" CTA badge if you prefer a non-dynamic, never-stale badge.

[Zahnentferner]

@hamzanazir27 , could you fix this?

[coderabbitai]

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

[Zahnentferner]

@hamzanazir27 , could you fix this?

[github-actions]

⚠️ This PR has merge conflicts.

Please resolve the merge conflicts before review.

Your PR will only be reviewed by a maintainer after all conflicts have been resolved.

📺 Watch this video to understand why conflicts occur and how to resolve them:
https://www.youtube.com/watch?v=Sqsz1-o7nXk