docs: update weights and frontmatter (#2000)

Co-authored-by: Antonio <bandantonio@users.noreply.github.com>

Author: bandantonio

docs/000-onboarding/ambassador-guide.md

@@ -38,4 +38,4 @@ Examples:
 - Our sincere gratitude and respect for your contributions!
 
 ### Additional resources
-[AsyncAPI Ambassador Program](../050-mentorship-program/ambassador-program/AMBASSADOR_PROGRAM.md)
+[AsyncAPI Ambassador Program](../020-governance-and-policies/ambassador-program/AMBASSADOR_PROGRAM.md)

docs/000-onboarding/documentarian-onboarding-guide.md

@@ -1,6 +1,6 @@
 ---
 title: Documentarian Onboarding Guide
-weight: 30
+# weight: 30
 ---
 
 🚧 This document is under construction.

docs/000-onboarding/how-to-contribute.md

@@ -1,6 +1,6 @@
 ---
 title: How to Contribute
-weight: 20
+# weight: 20
 ---
 
 🚧 This document is under construction.

docs/000-onboarding/where-to-contribute.md

@@ -1,6 +1,6 @@
 ---
 title: Where to Contribute
-weight: 10
+# weight: 10
 ---
 
 🚧 This document is under construction.

docs/010-contribution-guidelines/conventional-commits.md

@@ -42,7 +42,7 @@ The following are some of the most commonly used commit types:
 
 To maintain a clear and structured commit history, all PR titles must follow the Conventional Commits format. This ensures that commit messages and PRs are semantically meaningful and easy to understand.  
 
-A PR title that does not follow this format will be rejected by our [Linting bot](../../.github/workflows/lint-pr-title.yml), preventing the PR from being merged.  
+A PR title that does not follow this format will be rejected by our [Linting bot](https://github.com/asyncapi/community/blob/master/.github/workflows/lint-pr-title.yml), preventing the PR from being merged.  
 
 Therefore, you can use the following examples to guide you:
 

docs/styleguide/localization.md renamed to docs/011-styleguide/localization.md

@@ -210,7 +210,7 @@ They should be clear, optimized, and accessible.
 
   - **JPEG:** For photographs. Optimize for the web to balance quality and file size.
 
-- **Alt Text:** All `<img>` tags must have a descriptive alt attribute for screen readers. If an image is purely decorative, use `alt=""`. In markdown, use the exclamation mark, square brackets and parenthesis combo (`![]()`) to add images, ensure to use a decriptive alt text such as `![a blue bunny](bluebunny.png)`.
+- **Alt Text:** All `<img>` tags must have a descriptive alt attribute for screen readers. If an image is purely decorative, use `alt=""`. In markdown, use the exclamation mark, square brackets and parenthesis combo (`![]()`) to add images, ensure to use a descriptive alt text such as `![a blue bunny](bluebunny.png)`.
 
 - **Sizing:** Images should not exceed a maximum width of 800px to avoid overwhelming the content layout.
 

docs/011-styleguide/styling.md

@@ -5,8 +5,8 @@ weight: 10
 
 <p align="center"><strong>Technical Charter (the “Charter”)</strong></p>
 <p align="center">
-  for</br>
-  AsyncAPI Project a Series of LF Projects, LLC</br>
+  for<br />
+  AsyncAPI Project a Series of LF Projects, LLC<br />
   Adopted 03-19-2021, Amended 05-05-2025
 </p>
 

docs/020-governance-and-policies/CHARTER.md

@@ -34,7 +34,9 @@ Contribute funds to AsyncAPI through any of the following channels:
 
 <center>
 <a href="https://opencollective.com/asyncapi/contribute/platinum-sponsors-8119/checkout?interval=month&amount=2000" target="_blank">
-  <img src="https://opencollective.com/asyncapi/donate/button@2x.png?color=blue" width=300 />
+  <img src="https://opencollective.com/asyncapi/donate/button@2x.png?color=blue"
+       width="300"
+       alt="Donate to AsyncAPI via Open Collective" />
 </a>
 </center>
 
@@ -105,7 +107,9 @@ Every year we organize a conference that attracts many participants. Only last y
 
 
 <a href="https://opencollective.com/asyncapi/contribute/platinum-sponsors-8119/checkout?interval=month&amount=2000" target="_blank">
-  <img src="https://opencollective.com/asyncapi/donate/button@2x.png?color=blue" width=300 />
+  <img src="https://opencollective.com/asyncapi/donate/button@2x.png?color=blue"
+       width="300"
+       alt="Donate to AsyncAPI via Open Collective" />
 </a>
 
 ### Contact

docs/020-governance-and-policies/PROJECT_FUNDING.md

@@ -39,7 +39,7 @@ To improve and streamline the onboarding process for new contributors joining th
 ### Community Working Group Umbrella
 I would like to introduce the Community Working Group, which serves as an umbrella for all community initiatives and programs at AsyncAPI. We have been functioning unofficially as a working group, but it’s time to reorganize, increase visibility for our current programs, and establish a structured approach to how we work.
 
-``` mermaid
+```mermaid
 flowchart LR
     A["**Community Working Group**"] -- Chair By --> B("**Community Manager**")
     B --> C("**Community Programs and Initiatives**")
@@ -58,8 +58,7 @@ flowchart LR
     classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
     classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
     classDef Aqua stroke-width:1px, stroke-dasharray:none, stroke:#46EDC8, fill:#DEFFF8, color:#378E7A
-
-   ```
+```
 
 The community manager will oversee and chair the working group, which includes community builders responsible for building, leading, and running the programs.
 With this structured setup, we will say goodbye to community meetings and hello to the Community WG meeting; this is where we will provide updates on the different programs and the progress the builders are making.