Improve contribution guidelines

Author: albertospelta

_mydocs/contribute/daxlib-libraries.md

@@ -1,6 +1,6 @@
 ---
 layout:         page
-title:          Contribute to DAX Lib open-source libraries
+title:          Contribute to DAX Lib official libraries
 menu_title:     DAX Lib libraries
 published:      true
 date:           2025-10-17
@@ -9,8 +9,10 @@ order:          /05
 next_reading:   true
 ---
 
-**TO BE COMPLETED**
-To contribute to one of the DaxLib open-source libraries maintained by the DaxLib organization, follow these steps:
-1. Fork one of the dev-daxlib repos based corresponding to the library name.
-2. Apply the change, commit, and submit a Pull Request.
-3. Wait for review and approval.
+> This section is a work in progress and will be completed soon.
+
+To contribute to one of the official libraries maintained by the DAX Lib organization, follow these steps:
+
+1. Fork the repository for the library you want to contribute to. You can find all `dev-daxlib-*` repositories on [DAX Lib's GitHub page](https://github.com/orgs/daxlib/repositories).
+2. Make your changes, commit them, and submit a Pull Request.
+3. Wait for your contribution to be reviewed and approved.

_mydocs/contribute/fork-daxlib.md

@@ -9,11 +9,7 @@ order:          /03
 next_reading:   true
 ---
 
-A DAX library is a collection of DAX user-defined functions (UDFs) authored in TMDL format, along with metadata (such as library name, version, author, etc.) and optional files like a README or an icon.
-Development takes place in the [DaxLib GitHub repository](https://github.com/daxlib/daxlib/), where users can propose new libraries by submitting a pull request (PR).
-Once the pull request is approved, the library is automatically packaged as a ZIP file and published on [daxlib.org](https://daxlib.org/), making it available for browsing, installation, and use.
-
-You can follow these steps to add a new package to DAX Lib:
+For small libraries (a few functions), you can follow these steps to add a new package to DAX Lib:
 
 1. **Fork** the DAX Lib repository [https://github.com/daxlib/daxlib/fork](https://github.com/daxlib/daxlib/fork).
 
@@ -107,5 +103,5 @@ You can follow these steps to add a new package to DAX Lib:
 7. **Create a pull request** to publish the library on [daxlib.org](https://daxlib.org/)
 
     - Go [here](https://github.com/daxlib/daxlib/pull/new) to create a new pull request from your forked repository to the official DAX Lib repository.
-    - The pull request must be approved manually by DaxLib owners/maintainers.
+    - The pull request must be approved manually by DAX Lib owners/maintainers.
     - When the pull request is approved, the package is immediately published.

_mydocs/contribute/github-repo.md

@@ -9,12 +9,12 @@ order:          /04
 next_reading:   true
 ---
 
+> This section is a work in progress and will be completed soon.
+
 You don’t have to create a repository for your DAX library on daxlib.org, but it’s a smart move if you expect the library to grow. A GitHub repo helps you track issues, accept contributions, and manage changes easily.
 
 To create a GitHub repository for your DAX library, ensure you have a GitHub account; if not, create one. Then, follow the instructions at [https://github.com/daxlib/lib-quickstart-template](https://github.com/daxlib/lib-quickstart-template)
 
-**TODO**
-
 You can follow these steps to add a new package to DAX Lib:
 
 1. **Create a name** for your package following the [naming conventions](naming-conventions.md) for both the name of the library and the package.

_mydocs/contribute/index.md

@@ -4,12 +4,15 @@ title:          Contribute to DAX Lib
 menu_title:     Contribute
 published:      true
 date:           2025-08-14
-modified:       2025-10-15
+modified:       2025-10-17
 order:          /02
 next_reading:   true
 ---
 
-Depending on the size and complexity of your DAX library, you can choose one of the following methods to contribute it to DAX Lib:
+A DAX library is a collection of DAX user-defined functions (UDFs) written in TMDL format, along with metadata such as the library name, version, and author. It can also include optional files like a README or an icon. Users can contribute by submitting a pull request (PR). Once approved, the library is automatically packaged as a ZIP file and published on daxlib.org, making it available for browsing, installation, and use.
+
+Depending on your DAX library's size and complexity, you can choose one of the following methods to contribute it to DAX Lib:
+
 1. For small libraries (a few functions), follow the [Contribute Small Libraries to DAX Lib](fork-daxlib.md) guide.
 2. For medium to large libraries (more functions, more complex logic), consider creating a dedicated GitHub repository by following the [Contribute Medium-Large Libraries to DAX Lib](github-repo.md) guide.
-3. If you want to contribute to one DaxLib prefixed library that is maintained by the DaxLib organization, follow the [Contribute to DAX Lib open-source libraries](daxlib-libraries.md) guide.
+3. If you want to contribute to one DAX Lib official library that is maintained by the DAX Lib organization, follow the [Contribute to DAX Lib official libraries](daxlib-libraries.md) guide.

_mydocs/contribute/naming-conventions.md

@@ -21,8 +21,8 @@ When creating a new package for DAX Lib, it is important to follow specific conv
 
 2. **Package Folder Name** (⚠️ only for Small Libraries)
 
-      > This naming convention must be manually managed if you create a Small Library by forking the DAX Lib repository.
-      
+    > This naming convention only applies to Small Libraries created by forking the DAX Lib repository.
+    
     - The folder name for your package should be in lowercase letters and use dots to separate different levels of hierarchy.
 
       Example: for a package named `Contoso.Conversion`, the folder name should be:
@@ -69,7 +69,7 @@ When creating a new package for DAX Lib, it is important to follow specific conv
     - Do not use `DaxLib.` as a prefix for package name. This prefix is reserved for public open-source libraries of common use. Do not submit pull requests for new libraries using the `DaxLib.` prefix.
 
 6. **Folder Structure** (⚠️ only for Small Libraries)
-    > This naming convention must be manually managed if you create a Small Library by forking the DAX Lib repository.
+    > This naming convention only applies to Small Libraries created by forking the DAX Lib repository.
    - The **first level** structure should be a single letter (lowercase) corresponding to the first letter of the package name. This helps reduce the number of items in a single folder and keeps the repository organized.
    - The **second level** should be the package name (lowercase).
    - The **third level** should be the package version.