feat: add blender extension verison

.github/workflows/upload-assets.yml

@@ -22,7 +22,7 @@ jobs:
   #       id: draft_release
   #       uses: cardinalby/[email protected]
   #       with:
-  #         releaseName: Draft
+  #         releaseName: Upload
   #       env:
   #         GITHUB_TOKEN: ${{ github.token }}
 
@@ -69,7 +69,40 @@ jobs:
         with:
           upload_url: ${{ needs.draft_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
           asset_path: plugins/blender/package.zip
-          asset_name: Omoospace-Blender_${{ needs.draft_release.outputs.version }}.zip
+          asset_name: Omoospace-Blender_Addon_${{ needs.draft_release.outputs.version }}.zip
+          asset_content_type: application/zip
+
+  upload_blender_extension:
+    name: Upload Blender Extension
+    needs: draft_release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v4
+        with:
+          lfs: "true"
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: 3.11
+      - name: Zip Extension
+        run: |
+          cd plugins/blender
+          pip download omoospace==0.1.10 --dest omoospaceblender/wheels --only-binary=:all: --python-version=3.11
+          rm -r omoospaceblender/externalpackage
+          cp extension/__init__.py omoospaceblender/__init__.py
+          cp extension/preferences.py omoospaceblender/preferences.py
+          cp extension/blender_manifest.toml omoospaceblender/blender_manifest.toml
+          zip -r package.zip omoospaceblender
+      - name: Upload Release Asset
+        id: upload-release-asset
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          upload_url: ${{ needs.draft_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
+          asset_path: plugins/blender/package.zip
+          asset_name: Omoospace-Blender_Extension_${{ needs.draft_release.outputs.version }}.zip
           asset_content_type: application/zip
 
   upload_houdini_package:
@@ -78,7 +111,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.9", "3.10"]
+        python-version: ["3.9", "3.10", "3.11"]
     steps:
       - name: Checkout Code
         uses: actions/checkout@v4

README.md

@@ -4,11 +4,11 @@
 
 Omoospace is a directory structure guideline for digital creation works. Its aim is universality, flexibility, and semantics not only for large projects and teamwork but also for small projects and solo work. Whether it is a 3d modeling task or a series production, it all fits.
 
-If you are not sure how to design your project directory right, you can follow the omoospace rules, [click here to start](https://omoolab.github.io/Omoospace/latest/why_omoospace)
+If you are not sure how to design your project directory right, you can follow the omoospace rules, [click here to start](https://omoolab.github.io/Omoospace/latest/why-omoospace)
 
 We provide some DCC plugins for CG artists to easily manage your projects following omoospace rules.
 
 -   [Blender](https://omoolab.github.io/Omoospace/latest/plugins/blender)
 -   [Houdini](https://omoolab.github.io/Omoospace/latest/plugins/houdini)
 
-We also provide a python library for developing plugins, [read me for more info.](https://omoolab.github.io/Omoospace/latest/develop_plugin)
+We also provide a python library for developing plugins, [read me for more info.](https://omoolab.github.io/Omoospace/latest/develop-plugin)

docs/index.md

@@ -4,11 +4,11 @@
 
 Omoospace is a directory structure guideline for digital creation works. Its aim is universality, flexibility, and semantics not only for large projects and teamwork but also for small projects and solo work. Whether it is a 3d modeling task or a series production, it all fits.
 
-If you are not sure how to design your project directory right, you can follow the omoospace rules, [click here to start](https://omoolab.github.io/Omoospace/latest/why_omoospace)
+If you are not sure how to design your project directory right, you can follow the omoospace rules, [click here to start](https://omoolab.github.io/Omoospace/latest/why-omoospace)
 
 We provide some DCC plugins for CG artists to easily manage your projects following omoospace rules.
 
 -   [Blender](https://omoolab.github.io/Omoospace/latest/plugins/blender)
 -   [Houdini](https://omoolab.github.io/Omoospace/latest/plugins/houdini)
 
-We also provide a python library for developing plugins, [read me for more info.](https://omoolab.github.io/Omoospace/latest/develop_plugin)
+We also provide a python library for developing plugins, [read me for more info.](https://omoolab.github.io/Omoospace/latest/develop-plugin)

docs/omoospace_rules.md → docs/omoospace-rules.md

@@ -19,7 +19,7 @@ The rules are simple:
 4. Name source files with their creation objects as same as their outputs, those creation objects are the **Subspaces** of entire workspace.
 5. Write workspace profiles into **Omoospace.yml**, such as creator profiles, software versions, etc.
 
-![A diagram illustrating the structure of omoospace](assets/overview.png)
+![A diagram illustrating the structure of omoospace](/docs/assets/overview.png)
 
 A diagram illustrating the structure of omoospace
 
@@ -31,7 +31,7 @@ A diagram illustrating the structure of omoospace
 
 The nested subspaces can generate a tree-like graph that presents the structure of the entire project, as shown in the figure below.
 
-![Object tree](assets/object_tree.png)
+![Object tree](/docs/assets/object_tree.png)
 
 #### Name source files and directories with their creation objects as subspaces.
 
@@ -84,7 +84,7 @@ We call those source files and subspace directories **Entities** of their subspa
 
 The multi-level subspaces in `FilmA_SQ020_ModelB.blend` form a route from root to leaf: `FilmA > SQ020 > ModelB`. We call it **Subspace Route**.
 
-![Subspace route](assets/subspace_route.png)
+![Subspace route](/docs/assets/subspace_route.png)
 
 Suppose the entity subspace nodes contain its parent subspace nodes. They should overlap each other as much as possible, for example:
 

docs/plugins/blender.md

@@ -1 +1,2 @@
-# Blender
+# Blender
+