> For the complete documentation index, see [llms.txt](https://docs.myherb.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myherb.co.il/learning/myherb-onboarding-guide.md).

# MyHerb Contributor Guide

A practical guide for people contributing to MyHerb's learning, marketing or development work.

MyHerb brings together sustainability learning, public resources and practical tools. This guide explains the working principles for contributions to MyHerb's learning, marketing and development work.

<figure><img src="https://2587707612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOBKbQbCsvrrwr4PiaK7H%2Fuploads%2Fgit-blob-1c5a5a567016670f51e5795499a484f59d89ef43%2Ffuture1.jpeg?alt=media" alt=""><figcaption></figcaption></figure>

## Begin with the purpose

Aaron Levin built MyHerb around a simple belief: useful knowledge should lead to action. A contribution should help a reader understand a problem, make a decision or complete a practical next step.

The core values are:

* **Sustainability:** connect the work to a real environmental or social question.
* **Transparency:** separate evidence, interpretation and proposals.
* **Collaboration:** make the work understandable to the next person.
* **Innovation:** test new ideas, but describe their state honestly.

<figure><img src="https://2587707612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOBKbQbCsvrrwr4PiaK7H%2Fuploads%2Fgit-blob-4f7c5ba87f53798b8b793c9cfef6b0b18195132b%2F7.png?alt=media" alt=""><figcaption></figcaption></figure>

## Before starting work

1. Read the page, project history and any linked source material.
2. Confirm whether the item is published, in beta, in development or historical.
3. Define the reader and the one useful outcome the work should support.
4. Preserve original URLs, credits and source material.
5. Describe each concept, repository and vendor listing according to its current purpose and state.

## Marketing and editorial contributions

Keep the writing specific and natural. Check every number, quotation, result and relationship. Explain what the reader can do, then link to the real destination. Do not invent customers, testimonials or environmental benefits.

## Development contributions

Start from the user's actual task. Reuse working code, keep data and customer boundaries clear, and test through the real entry point. The work is ready when that task succeeds reliably.

<figure><img src="https://2587707612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOBKbQbCsvrrwr4PiaK7H%2Fuploads%2Fgit-blob-0d82ad43aec9f4e658852c915c0521f4cde41748%2Fimage%20(4).png?alt=media" alt=""><figcaption></figcaption></figure>

## Handover checklist

* State what changed and why.
* Record the source and current status.
* Test links, mobile layout and the main action.
* Name anything that remains unverified.
* Leave a clear rollback or recovery path for published work.

<figure><img src="https://2587707612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOBKbQbCsvrrwr4PiaK7H%2Fuploads%2Fgit-blob-c7cccde4eb817758e73753200da203a7e90cee03%2Fcollaborative321.jpeg?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
For public material, begin with the [Knowledge Base](https://docs.myherb.co.il/knowledge-base/knowledge-base.md) and the [Brand Voice](https://docs.myherb.co.il/about-us/brand-voice-of-myherb-a-comprehensive-exploration.md).
{% endhint %}
