CONTRIBUTING: Add guidelines for module documentation and versioning.

Signed-off-by: Jos Verlinde <[email protected]>

Author: Josverl

CONTRIBUTING.md

@@ -87,6 +87,40 @@ specific conventions and guidelines for micropython-lib:
   packages](README.md#installing-packages-from-forks) in your Pull Request
   description.
 
+### Module documentation
+
+Each package in micropython-lib is encouraged to include documentation in
+the form of docstrings in the code itself. The top-level docstring in the main
+module or package should provide an overview of the package's functionality,
+usage examples, and any important notes or caveats.
+
+Note that the docstrings should be concise and relevant, even though they will
+not be included in the cross-compiled bytecode and will not impact the size of
+the module when installed via `mip`.
+
+When writing docstrings, please follow these guidelines:
+* Use triple double quotes (`"""`) for docstrings.
+* Multi-line docstrings should place the starting and ending triple quotes on
+  their own lines.
+* Start with a brief summary of the module's purpose.
+* Include usage examples where appropriate (indent examplecode blocks with 4
+  spaces).
+* Use proper indentation for multi-line docstrings to align with the code block.
+
+### Module versioning
+
+Each package in micropython-lib should include a `manifest.py` file that
+specifies metadata about the package, including its version. The version
+management is intentionally manual to ensure package stability and prevent
+accidental version bumps. When making changes to a package that affect its
+functionality or API, please update the version in `manifest.py`. The
+`tools/build.py` script will detect new versions and add them to the index, but
+won't increment versions automatically
+
+> [!NOTE]
+> Changes to docstrings or comments that do not change the generated bytecode
+> should not change the version.
+
 ### Publishing packages from forks
 
 You can easily publish the packages from your micropython-lib