added missing content and fix toc active

Signed-off-by: Rajesh-Nagarajan-11 <rajeshnagarajan36@gmail.com>

Author: Rajesh-Nagarajan-11

src/collections/handbook/community/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Community"
+title: "Community Guidelines"
 description: "A MeshMate is an experienced Layer5 community member, who will be available to guide you as you explore the various projects and find your areas of interest."
 type: Handbook
 contents:

src/collections/handbook/github-process/index.mdx

@@ -87,38 +87,187 @@ Area labels specify which part of the project an issue or PR relates to—such a
 ### Component Labels
 Component labels indicate which software module or subsystem is affected by an issue. This ensures issues are routed to the right maintainers and allows more detailed filtering beyond the broader area labels. Attach a component label when your issue/PR impacts a specific module (e.g., a CLI tool, API, or pattern engine).
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>component/api</td><td>API related</td><td>#3a0485</td></tr>
+      <tr><td>component/mesheryctl</td><td>Meshery CLI related</td><td>#3a0486</td></tr>
+      <tr><td>component/ui</td><td>UI component related</td><td>#3a0486</td></tr>
+      <tr><td>component/filters</td><td>Filters related</td><td>#3a0486</td></tr>
+      <tr><td>component/patterns</td><td>Patterns related</td><td>#3a0486</td></tr>
+      <tr><td>component/meshsync</td><td>MeshSync component related</td><td>#3a0487</td></tr>
+      <tr><td>component/meshery-perf</td><td>Meshery-perf related</td><td>#3a0488</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Programming Language Labels
 Programming language labels highlight the primary language used in the issue or PR. This helps contributors looking for language-specific work, and aids in code review or help requests. Use a programming language label if the change, bug, or feature is specific to a particular language (e.g., a Go backend bug, a JavaScript UI enhancement).
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>language/go</td><td>Golang related</td><td>#16e2e2</td></tr>
+      <tr><td>language/javascript</td><td>Javascript</td><td>#16e2e3</td></tr>
+      <tr><td>language/ruby</td><td>Ruby</td><td>#16e2e4</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### PR (Pull Request) Labels
 PR labels manage the state or special requirements of a pull request, like indicating it's a draft, dependent on others, or not yet ready for merging. Apply a PR label if your pull request isn't ready, should not be merged, updates dependencies, or is on hold.
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>pr/dependencies</td><td>Updates addressed dependencies</td><td>#0366d5</td></tr>
+      <tr><td>pr/do-not-merge</td><td>Not ready for merging</td><td>#0366d6</td></tr>
+      <tr><td>pr/draft</td><td>Work in progress/draft PR</td><td>#0366d7</td></tr>
+      <tr><td>pr/on hold</td><td>PR/Issue on hold</td><td>#0366d8</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Issue Process & Status Labels
 These labels show the current status of an issue—such as blocked, duplicate, in need of a design, or if an action (like an invitation) should be triggered. Some are used by bots to automate reminders or mark stale issues. Apply these when the situation applies (e.g. "blocked" if work can't proceed, "design required" if more planning is needed).
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>issue/invite</td><td>Invitation for author to join GH org</td><td>#eeeeee</td></tr>
+      <tr><td>issue/blocked</td><td>Issue is blocked</td><td>#eeeeee</td></tr>
+      <tr><td>issue/design required</td><td>Requires a design prior to proceeding</td><td>#eeeeee</td></tr>
+      <tr><td>issue/duplicate</td><td>Issue or PR already exists</td><td>#eeeeee</td></tr>
+      <tr><td>issue/invalid</td><td>This doesn't seem right</td><td>#eeeeee</td></tr>
+      <tr><td>issue/stale</td><td>No activity for an extended period (often applied automatically)</td><td>#eeeeee</td></tr>
+      <tr><td>issue/tweet</td><td>Posts (for social or outreach)</td><td>#eeeeee</td></tr>
+      <tr><td>issue/remind</td><td>Reminder comment to assignee</td><td>#eeeeee</td></tr>
+      <tr><td>issue/willfix</td><td>Issue will be worked on ("stale" bot skips)</td><td>#eeeeee</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Kind Labels
 Kind labels classify the general type of change or discussion: bug, feature, chore, enhancement, epic, question, or proposal. This improves searchability and helps teams organize their workflows. Use the kind label that best describes your issue or PR.
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>kind/bug</td><td>Something isn't working</td><td>#088073</td></tr>
+      <tr><td>kind/child</td><td>Child of a larger Epic</td><td>#088074</td></tr>
+      <tr><td>kind/chore</td><td>Maintenance or other necessary task</td><td>#088075</td></tr>
+      <tr><td>kind/enhancement</td><td>Improvement to an existing feature</td><td>#088076</td></tr>
+      <tr><td>kind/epic</td><td>An umbrella issue, covers many issues</td><td>#088077</td></tr>
+      <tr><td>kind/feature</td><td>New major feature or request</td><td>#088078</td></tr>
+      <tr><td>kind/proposal</td><td>Suggestion or proposal for change</td><td>#088079</td></tr>
+      <tr><td>kind/question</td><td>Explanation or further info requested</td><td>#088080</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Priority Labels
 Priority labels help teams triage and allocate attention, making it clear which issues are urgent and which can wait. Always apply a priority label, adjusting as priorities shift or as issues are escalated or downgraded.
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>priority/urgent</td><td>Needs immediate attention</td><td>#f60205</td></tr>
+      <tr><td>priority/high</td><td>High priority issue</td><td>#d60205</td></tr>
+      <tr><td>priority/low</td><td>Lower priority, can wait</td><td>#a60205</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Service Mesh Labels
 Service mesh labels point out which mesh technology or ecosystem the issue pertains to. This is vital for projects supporting multiple meshes, enabling modular attention and expertise. Use these when your change or report is specific to one mesh (like Istio or Linkerd).
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>service-mesh/app-mesh</td><td>App Mesh</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/consul</td><td>Consul</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/cpx</td><td>CPX</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/istio</td><td>Istio</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/kuma</td><td>Kuma</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/linkerd</td><td>Linkerd</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/maesh</td><td>Maesh</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/nginx</td><td>NGINX SM</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/nsm</td><td>NSM</td><td>#57b6cc</td></tr>
+      <tr><td>service-mesh/tanzu</td><td>Tanzu</td><td>#57b6cc</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Help & Onboarding Labels
 Help labels signal issues where some support is needed, or which are especially suitable for newcomers. These labels foster open source engagement and make onboarding easier for new contributors. Apply these to issues where you'd appreciate community help (`help wanted`) or for issues that are clearly documented, small in scope, and ideal for first-timers (`good first issue`).
 
+<div className="table-container">
+  <table>
+    <thead>
+      <tr><th>Label</th><th>Description</th><th>Color</th></tr>
+    </thead>
+    <tbody>
+      <tr><td>help wanted</td><td>Maintainers need help here</td><td>#35f48e</td></tr>
+      <tr><td>good first issue</td><td>Good for new contributors</td><td>#7057ff</td></tr>
+    </tbody>
+  </table>
+</div>
+
 ### Best Practices & Example
 - **Apply all relevant labels**: an issue may belong to an area, a component, a kind, have a priority, AND be language-specific.
 - **Update labels as issues evolve**: don't hesitate to add or remove as information changes.
-- **When in doubt, ask!**: The <a href="https://layer5.io/community">Layer5 community Slack</a> is a welcoming place.
+- **When in doubt, ask!**: The [Layer5 community Slack](https://layer5.io/community) is a welcoming place.
+
+**Example:**
+
+If you find a documentation error regarding Meshery's CLI, that's an easy fix, you might use these labels:
 
-**Example:**<br />
-If you find a documentation error regarding Meshery's CLI, that's an easy fix, you might use these labels:<br/>
 `area/docs, component/mesheryctl, kind/bug, priority/low, good first issue`
 
 ### Questions or Suggestions?
-Labels missing? Unclear usage? Open a discussion or tag a maintainer in your issue, or bring it up in <a href="https://layer5.io/community">community Slack</a>.
+Labels missing? Unclear usage? Open a discussion or tag a maintainer in your issue, or bring it up in [community Slack](https://layer5.io/community).
+
+### List for Pull Requests
+The following list of pull request labels will be used to both indicate purpose or status of the PR to maintainers, and significantly, they will be used in conditional logic during workflow execution to determine the PR's appropriate path through the CI flow.
+
+- **Refactor** - Chore related pull request
+- **Fix** - Bug fixes PRs
+- **On-hold** - PR needs review before merging or it needs to behold until a specific issue is fixed.
+- **Dependabot** - All dependabot related automated PRs
+- **release** - identifies that a release is / will be made
+- **Draft** - PR is in draft state, GitHub provides a way for the draft state but having a label will help us in triage purposes.
+- **Approved** - Indicates a PR has been approved by approver form all required OWNERS files. #51ed31
+- **help wanted** - Extra attention is needed #008672
+- **needs-ok-to-test** -  #d60c6a
+- **awaiting review** - The PR is ready for the reviewer to review. #fbca04
+
+Improving the build times through conditional logic that will skip sections of the ci.yml, unless these labels are present:
+
+- **docs** -  build the Jekyll site for Meshery documentation
+- **component/mesheryctl** - build the Meshery CLI
+- **area/ui** -  build the Meshery UI
+- **component/meshery-server** - Assumed that Meshery Server should always be build, but this is not the case.
 
 ### Bots
 Layer5 uses the following bots:
@@ -131,4 +280,4 @@ Layer5 uses the following bots:
 - Labeler.yml
 - label-commenter.yml
 
-Good resource - <a href="https://github.com/sdras/awesome-actions#pull-requests">https://github.com/sdras/awesome-actions#pull-requests</a>
+Good resource - [https://github.com/sdras/awesome-actions#pull-requests](https://github.com/sdras/awesome-actions#pull-requests)

src/collections/handbook/writing-program/index.mdx

@@ -195,27 +195,48 @@ Do you want to document your recent effort in implementing a new feature? Do you
   </div>
 </div>
 
-## Content Guidelines
 
-- **Original**: All content must be original and not published elsewhere
-- **Technical**: Focus on technical topics related to cloud native, Kubernetes, service mesh, and related technologies
-- **Helpful**: Provide practical value to readers through tutorials, guides, or insights
-- **Well-written**: Follow good writing practices with clear structure and proper grammar
-- **Accurate**: Ensure all technical information is correct and up-to-date
 
-## Recognition
+## What are some suggested topics?
 
-Published authors receive:
-- **Byline**: Credit on published content
-- **Profile**: Featured on the <Link to="/community/members">community members</Link> page
-- **Badge**: Writer badge on your community profile
-- **Promotion**: Social media promotion of your content
-- **Swag**: Layer5 swag for significant contributions
+Here are some suggested topics to get you started. If you have an idea that isn't listed here or if you have any question, please let us know on our [Discuss Forum](https://discuss.layer5.io/) / [Slack Channel](https://layer5io.slack.com/).
+
+- **DevOps/Observability/Kubernetes:**
+  - Distributed Tracing in Context of Meshery's Architecture.
+  - One-stop Cloud Native Market Place - Meshery Catalog.
+  - Interpreting your Cloud Native Performance - SMP.
+  - Creating and Deploying your first application with Kanvas.
+  - Load generation and Load balancing.
+  - DevOps and Platform Engineering.
+  - Beginners guide to Meshmodel.
+  - Enhancing Microservices Observability with Meshery and Prometheus.
+
+- **Community:**
+  - Building Bridges, Not Walls: The Power of Open Source Collaboration.
+  - A Deep Dive into Meshery's Contribution to Cloud Native Ecosystem.
+  - Open Source Sustainability: Funding Models for Long-Term GitHub Projects.
+  - Importance to an open source community.
+  - Beyond Code: The Unsung Heroes of Open Source - Documenters, Testers, and Designers.
+  - Open Source Alchemy: Transforming Community Contributions into Gold.
+  - Collaborative Open Source Development: Inside the Community of Layer5.
+
+## How to Submit and Review Your Writing?
+
+The Writing Program offers writers two convenient ways to get their writings reviewed by Community. Whether you prefer working with Google Docs or contributing directly to the website, we've got you covered. This structured guide will walk you through both options, ensuring that your valuable content is reviewed effectively.
+
+1. **Google Docs Review:**
+
+   If you prefer a straightforward approach, start by crafting your blog article within [Google Docs](https://docs.google.com/), ensuring it's well-structured and error-free. Share the document with us by adding it to the [Community Drive](https://drive.google.com/drive/folders/1o6ZSqCq1QUJmLIjl_Y0VgT_azNbgg1W2), we will provide feedback directly within the Google Doc. Engage in discussions to refine your content collaboratively. Once thoroughly reviewed, prepare your submission according to community guidelines.
+
+2. **Website Contribution Review:**
+
+   For those comfortable with local website development, contribute directly to the community website. [Set up your local environment](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md), create a blog post adhering to specified guidelines, and submit it via a Pull Request on [GitHub](https://github.com/layer5io/layer5/). Reviewers will provide feedback, and you'll refine your post collaboratively. Upon completion, maintainers will merge your blog post into the website repository, celebrating your contribution.
 
 ## Additional Resources
 
-- <a href="https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md#adding-a-resource">Contributing to Layer5 Resources</a>
-- Join the <a href="https://discuss.layer5.io/">Layer5 Discussion Forum</a>
+- [Contributing to Layer5 Blogs](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md#adding-a-blog-post)
+- [Contributing to Layer5 Resources](https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md#adding-a-resource)
+- [View open Writing Program issues](https://github.com/layer5io/layer5/labels/area%2Fblog)
+- Join the [Layer5 Discussion Forum](https://discuss.layer5.io/)
 - Explore our <Link to="/resources">Resource Library</Link>
 - <Link to="/learn">Learn Cloud Native</Link>
-- Connect with us on <a href="https://slack.layer5.io/">Slack</a>

src/sections/Community/Handbook/handbook-single/HandbookTOC.js

@@ -18,8 +18,7 @@ const HandbookTOC = ({ pages, currentSlug }) => {
             <li key={index}>
               <Link
                 to={page.fields.slug}
-                className="toc-sub-heading toc-sub-inline"
-                activeClassName="active"
+                className={`toc-sub-heading toc-sub-inline${page.fields.slug === currentSlug ? " active" : ""}`}
               >
                 {page.frontmatter.title}
               </Link>