Update docs from text-forge/text-forge: 632e41231a7fd0c92f1d508f1a90ef2216037af1

Author: github-actions[bot]

docs/contribution_types.md

@@ -0,0 +1,33 @@
+# Contribution Types
+
+This is a list of available types for contributing, you can choose your contribution type from this list based on your
+abilities or find new way to contribute, feel free!
+
+!!! Note
+
+    You can share your ideas about what you will do in [discussions](https://github.com/text-forge/text-forge/discussions)
+    to receive others comments to be sure about what you want or get tips.
+
+!!!
+
+## Programming
+
+This section is for peoples with programming experience, specially who know about [OOP](https://www.bing.com/ck/a?!&&p=884f008f70c8bd91a7398ae34eaeff00571a7db0f1fe4d255995619348c533e4JmltdHM9MTc1MjM2NDgwMA&ptn=3&ver=2&hsh=4&fclid=09a8c98b-e870-67ad-2bfe-dce3e96466d1&psq=wikipedia+oop&u=a1aHR0cHM6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kvT2JqZWN0LW9yaWVudGVkX3Byb2dyYW1taW5n&ntb=1)
+and modularity, with knowledge about GDScript, C# or other languages Godot supports.
+
+### Codebase Review
+
+- Audit every file for adherence to style, modularity, Text Forge philosophy, and Godot best practices.
+- Identify duplicate, dead, or outdated code and remove them.
+
+### Repository Restructuring
+
+- Consider in-repo documentation (README, CONTRIBUTING, architecture overview).
+- Improve folder structure for modes, core, plugins, and utils.
+
+!!! Note
+
+    Change files structure needs change code in most cases, be sure your changes will not break anything!
+
+!!!
+