Initial commit.

.gitignore

@@ -0,0 +1 @@
+*.blend1

.vscode/settings.json

@@ -0,0 +1,7 @@
+{
+    "spellright.language": [],
+    "spellright.documentTypes": [
+        "latex",
+        "plaintext"
+    ]
+}

README.md

@@ -4,89 +4,73 @@ A collection of my commonly used blender node groups (shading nodes, geometry no
 
 ## Getting started
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+To get the nodes either download the respecive blend file directly or download the full repository as a zip file using
+this button (![download-icon](icons/download.png)) above.
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+To easily get access to the provided nodes, activate the
+[Node Presets](https://docs.blender.org/manual/en/dev/addons/node/node_presets.html) add-on and configure it to parse
+one of the subdirectories (e.g. [shadingNodes](./shadingNodes)).
 
-## Add your files
+As soon as the asset browser supports node groups in an official release, this organization might change a bit to
+support the asset workflow.
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+# List of nodes
 
-```
-cd existing_repo
-git remote add origin https://gitlab.com/subdivided_xyz/nodes_xyz.git
-git branch -M main
-git push -uf origin main
-```
+## Shading nodes
 
-## Integrate with your tools
+### [HSV_Object_Variation](shadingNodes/shadingNodeGroupCollection.blend)
 
-- [ ] [Set up project integrations](https://gitlab.com/subdivided_xyz/nodes_xyz/-/settings/integrations)
+> This node can be integated whenever a whole set of instances is being shaded (e.g. a bunch of rocks). It allows to
+> vary each instance in hue, saturation and value.
 
-## Collaborate with your team
+### [If](shadingNodes/shadingNodeGroupCollection.blend)
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+> Switches between 2 vector values based on a boolean input.
 
-## Test and Deploy
+### [Object Size](shadingNodes/shadingNodeGroupCollection.blend)
 
-Use the built-in continuous integration in GitLab.
+> A node, that can be used when shading multiple instances, that are scaled in size. Through this node, it's possible
+> to get a factor of the size differences between the instances and align texture coordinates based on this factor.
 
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+### [Spherical Coords](shadingNodes/shadingNodeGroupCollection.blend)
 
-***
+> A node, that takes e.g. a shading position and calculates the angles of spherical coordinates.
 
-# Editing this README
+### [Voronoi Based Noise](shadingNodes/shadingNodeGroupCollection.blend)
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!).  Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+> A kind of noise node, that is based on a voronoi pattern
 
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+## Geometry nodes
 
-## Name
-Choose a self-explaining name for your project.
+### [Tissue](geoNodes/tissue.blend) (Blender 3.1)
+> This is a geo node group, that mimicks what the
+> [Tissue](https://docs.blender.org/manual/en/latest/addons/mesh/tissue.html) addon provided with blender is doing.
 
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+### [Deform Objects to curve](geoNodes/deformObjectsToCurve.blend) (Blender 3.1)
 
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+> This node group aligns a set of objects on a curve and additionally allows deforming them along the curve itself.
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+### [BBoxField](geoNodes/deformObjectsToCurve.blend) (Blender 3.1)
 
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+> Contained within the `deformObjectsToCurve.blend` file, this node provides a field output, that defines the bounding
+> box of each instance being provided through the Instances parameter.
 
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+### [BoxDeform](geoNodes/deformObjectsToCurve.blend) (Blender 3.1)
 
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+> Also contained within the `deformObjectsToCurve.blend`  file, this node takes a normalized geometry (e.g. contained
+> within the [0..1] cube) and interpolates the point positions to a box provided by the 8 corner input parameters.
 
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
+### [Lerp](geoNodes/deformObjectsToCurve.blend) (Blender 3.1)
 
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
+> Contained within the 'deformObjectsToCurve.blend` file, this is a simple node, that interpolates between 2 vector
+> values based on a numeric input t, which is given in the range of [0..1].
 
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+### 
 
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+# Assets
 
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
+The repository also will contain a list of small assets, that can be reused in multiple projects.
 
-## License
-For open source projects, say how it is licensed.
+## Eye
 
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+[<img src="assets/eye.png" width=200/>](assets/eye.blend)