[Docs] Add Extensions section to Meshery GitHub Org overview

[Utkarsh-sharma47]

Description

Adds a new Extensions section to the Meshery GitHub organization overview.

Changes

• Added Meshery Extensions section to profile README
• Added Meshery Extensions logo asset
• Added links to:
  • meshery.io/extensions
  • meshery-extensions GitHub organization
  • CNCF blog on Meshery's expanding ecosystem
• Highlighted several extension repositories and their purpose

Fixes #61

[gemini-code-assist]

Code Review

This pull request adds a new 'Extensions' section to the profile README, showcasing various Meshery extensions with descriptions and status badges, and introduces a new color SVG asset for Meshery Extensions. Feedback on the README changes includes correcting invalid HTML5 attributes, specifically changing border="0px" to border="0" on the table element, and moving alt attributes from anchor (<a>) tags to their nested image (<img>) tags to ensure proper validation and accessibility.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

In HTML5, the border attribute on <table> elements only accepts a value of "0" or "1". Specifying units like px (e.g., 0px) is invalid HTML. Please use border="0" instead.

Suggested change

<table border="0px" align="center">

<table border="0" align="center">

[gemini-code-assist]

The alt attribute is not a valid attribute for <a> (anchor) elements in HTML. It should be placed on the nested <img> elements instead to ensure proper HTML validation and accessibility. Please apply this fix here and to the other repository listings below (lines 156-160, 171-175, 186-190, 201-205, and 216-220).

Suggested change

	<p align="left"><a href="https://github.com/meshery-extensions/meshery-extensions-packages/graphs/contributors"
	alt="GitHub contributors"><img
	src="https://img.shields.io/github/contributors/meshery-extensions/meshery-extensions-packages.svg" /></a>
	<a href="https://github.com/meshery-extensions/meshery-extensions-packages/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22" alt="meshery-extensions-packages repo issues with help wanted label">
	<img src="https://img.shields.io/github/issues/meshery-extensions/meshery-extensions-packages/help%20wanted.svg?color=informational" /></a>
	<p align="left"><a href="https://github.com/meshery-extensions/meshery-extensions-packages/graphs/contributors"><img
	src="https://img.shields.io/github/contributors/meshery-extensions/meshery-extensions-packages.svg" alt="GitHub contributors" /></a>
	<a href="https://github.com/meshery-extensions/meshery-extensions-packages/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22">
	<img src="https://img.shields.io/github/issues/meshery-extensions/meshery-extensions-packages/help%20wanted.svg?color=informational" alt="meshery-extensions-packages repo issues with help wanted label" /></a>

[Utkarsh-sharma47]

Hi maintainers,

I've completed the implementation for this issue and opened this PR for review. Please let me know if any changes or adjustments are needed.

Thank you.

[leecalcote]

Look at meshery/meshery readme for and example light and dark mode support.

[Utkarsh-sharma47]

Thanks for the feedback @leecalcote.

I've updated the Extensions section to support both light and dark modes following the pattern used in the meshery/meshery README.

[chellej]

@Utkarsh-sharma47 please address the merge conflicts.

[Utkarsh-sharma47]

Thanks for the feedback.

I've rebased the branch onto the latest upstream master and resolved the merge conflict. The Extensions section also now supports both light and dark mode rendering following the existing Meshery README pattern.

Please let me know if any further changes are needed.

[Utkarsh-sharma47]

@leecalcote , Thanks for the feedback and for pointing me to the meshery-extensions organization.

After rebasing onto the latest master and comparing with #58, I realized the two approaches are slightly different. My intention with this PR was to focus on highlighting repositories that are actively part of the extensions org itself (for example, kanvas-snapshot, helm-kanvas-snapshot, meshery-extensions-packages, and meshery-nighthawk), while #58 seems more focused on providing a broader extensions ecosystem overview.

I'm happy to adjust the implementation either way. Do you think it would make sense to combine elements of both approaches, or would you prefer that this PR align more closely with the structure introduced in #58?

I'd appreciate your guidance on the preferred direction before making further changes.

[Utkarsh-sharma47]

Hi @leecalcote and @chellej,

Just following up. The requested changes have been addressed, merge conflicts resolved, and all checks are passing.

I'd appreciate a review when you have a chance. Thanks!