Update Houdini addon docs

website/docs/admin_hosts_houdini.md

@@ -4,33 +4,167 @@ title: Houdini Admin docs
 sidebar_label: Houdini
 ---
 
+import ReactMarkdown from "react-markdown";
+import versions from '@site/docs/assets/json/Ayon_addons_version.json'
+
+<ReactMarkdown>
+{versions.Houdini_Badge}
+</ReactMarkdown>
+
+
+## General
+
+### Add Self Publish Button
+
+Enabling this setting will cause Houdini creator to add a **self publish button** when creating new publish instances. More Info on how how the **self publish button** works [here](artist_hosts_houdini#ayon-publishing-process)
+
+![general_settings_self_publish_button](assets/houdini/admin/general_settings_self_publish_button.png)
+
+### Update Houdini Vars on context change
+
+Allows admins to have a list of vars (e.g. JOB) with (dynamic) values that will be updated on context changes, e.g. when switching to another asset or task.
+
+:::info
+**JOB** Var: If `JOB` is present in the Houdini var list and has an empty value, Ayon will set its value to `$HIP`
+:::
+
+![update-houdini-vars-context-change](assets/houdini/admin/update-houdini-vars-context-change.png)
+
+1. **Update Houdini vars on context change :** Disabling this setting will leave all Houdini vars unmanaged and thus no context update changes will occur.
+2. **(+) :** add new Houdini variable
+3. **Var :** The Houdini variable you want to add. No need to include `$`.
+  > For consistency reasons we always force all vars to be uppercase. e.g. `myvar` will be `MYVAR`
+4. **Value :** The value you want Ayon to maintain. 
+  > Using template keys is supported but formatting keys capitalization variants is not, e.g. `{Asset}` and `{ASSET}` won't work. For a list of available template keys go to [available template keys](#what-template-keys-are-available-for-use-in-houdini-settings).
+1. **Treat as directory :** If activated, Ayon will consider the given value as a path of a folder.
+  > If the folder does not exist on the context change it will be created by this feature so that the path will always try to point to an existing folder.
+
+## Color Management (ImageIO)
+
+Allows admins to override the global color management settings, check [Host specific overrides](https://ayon.ynput.io/docs/admin_colorspace#host-specific-overrides)
+
+![houdini-color-management](assets/houdini/admin/houdini-color-management.png)
+
 ## Shelves Manager
-You can add your custom [Shelves](https://www.sidefx.com/docs/houdini/shelf/index.html) into Houdini by setting your shelf sets, shelves and tools in **Houdini -> Shelves Manager**.
-![Custom menu definition](assets/houdini-admin_shelvesmanager.png)
-
-The Shelf Set Path is used to load a .shelf file to generate your shelf set. If the path is specified, you don't have to set the shelves and tools.
-
-
-![Shelves Creation](assets/settings_project_houdini_shelves.png)
-1. **Shelf set name:** enter the name of the **shelf set** you want to import or create.
-2. **Shelf Set Path (optional):** enter the Shelf set path (on Windows, MacOs or Linux) (optional).
-3. **(+/-) :** add or delete a **shelf set**.
-4. **(+/-) :** add a **shelf** to the **shelf set**.
-5. **(+/-) :** add a **tool** to this shelf.
-6. **Shelf Name:** enter the **shelf**'s name you want to create.
-7. **Name:** enter the **tool** name you want to add to this **shelf**.
-8. **Script:** enter the tool's script to import it.
-9. **Icon:** add the tool's icon.
-10. **Help:** add a help text to the tool. It shows when you rest the cursor on the tool
-11. **⇅:** change the **shelf** order into the **shelf set**.
-12.  **⇅:** change the **tool** order in it **shelf**.
-
-# Creator plugins
+
+Allows admins to add studio's [Shelves](https://www.sidefx.com/docs/houdini/shelf/index.html) and scripts into Houdini. 
+
+### Different Modes
+
+:::info
+You have two options to define a shelf which are mutually exclusive from one another:
+
+- If you set a Shelf Set Path that shelf is loaded, any scripts defined below it are ignored.
+- If you have no Shelf Set Path, then it'll create a shelf dynamically from the Shelf Scripts.
+:::
+
+Shelves manager works in two modes, it's either option 1 or 2.
+
+1. Add a `.shelf` file by only setting the `Shelf Set Name` and `Shelf Set Path`.
+  ![houdini_shelves_manager_mode_1](assets/houdini/admin/houdini_shelves_manager_mode_1.png)
+
+2. **OR** set the `Shelf Set Name` and create `shelf definitions` with shelf scripts dynamically.
+  > *Currently, Ayon just adds the new shelf definition in `default.shelf`*
+
+  ![houdini_shelves_manager_mode_2](assets/houdini/admin/houdini_shelves_manager_mode_2.png)
+
+
+### Shelves Example
+
+:::info
+Using template keys is supported but formatting keys capitalization variants is not, e.g. `{Asset}` and `{ASSET}` won't work. For a list of available template keys go to [available template keys](#what-template-keys-are-available-for-use-in-houdini-settings).
+:::
+
+In this example I made two shelves: 
+1. `Null Shelf` which gets loaded from my pre-defined `null_shelf.shelf` file.
+2. `Ayon Shelf` which includes my script `Say Hello`.
+
+![houdini_shelves_manager_example](assets/houdini/admin/houdini_shelves_manager_example.png)
+
+
+## Creator plugins
 Enable or disable the plugins. Some of them have extra options such as defining the default subsets names.
 
-**Plugins list:** Create Arnold Ass, Create Alembic Camera, Create Composite (Image Sequence), Create Point Cache, Create Redshift ROP, Create Remote Publish, Create VDB Cache, Create USD, Create USD Model, Create USD Shading Workspace, Create USD Render.
+- Create Alembic Camera
+- Create Arnold Ass
+- Create Arnold ROP
+- Create Composite (Image Sequence)
+- Create Houdini Digital Asset
+- Create Karma ROP
+- Create Mantra ROP
+- Create PointCache (Abc)
+- Create PointCache (Bgeo)
+- Create Redshift Proxy
+- Create Redshift ROP
+- Create Review
+- Create Static Mesh
+- Create USD (experimental)
+- Create USD render (experimental)
+- Create VDB Cache
+- Create VRay ROP
 
-# Publish plugings
+## Publish plugins
 Enable or disable the plugins executed at publishing.
 
-**Publish plugins list:** Validate Workfile Paths, ValidateContainers.
+- Collect Rop Frame Range
+- Validate Latest Containers
+- Validate Mesh is Static
+- Validate Review Colorspace
+- Validate Subset Name
+- Validate Unreal Static Mesh Name
+- Validate workfile paths settings
+
+### Collect Rop Frame Range
+
+Disable this if you want the publisher to ignore start and end handles specified in the asset data for publish instances.
+> Artists are allowed to override this value in the publisher UI.
+
+![houdini_publish_plugins_collectors_frame_range](assets/houdini/admin/houdini_publish_plugins_collectors_frame_range.png)
+
+---
+
+## FAQ
+
+### When will I need to modify Houdini addon code ?
+We've spent a lot of time making it possible to customize Houdini addon from settings.
+e.g. you can add your studio's menus, tools and digital assets from settings. 
+
+Still, you may need to modify Ayon addons only when :  
+- Adding/Modifying/Customizing Launch Hooks
+- Registering new Callbacks
+- Adding/Modifying/Customizing plugins (create, publish, load, Actions)
+- Adding a new Ayon launcher tray tool
+
+### How to add my menus, tools and digital assets to Houdini ?
+First, consider adding custom shelves as you can easily use them to share a lot of tools with your team.
+However, if you need to add custom python libraries or custom OTLs or custom menus, updating environment variables is your way to make them available to your team. 
+
+e.g., 
+- `PYTHONPATH` to add a custom python library path
+- `HOUDINI_MENU_PATH` to add a custom menu path
+- `HOUDINI_OTL_PATH` to add a custom digital assets path
+
+Ayon allows you to add environment variables as:
+1. Global environment variable (it will be available for all DCCs)
+2. Application specific (it will be available for a particular DCC)
+3. Application variant specific (it will be available for a particular DCC version)
+4. Tool (it will be available on demand per DCC per project per asset)
+
+For a detailed guide visit: [Ayon/Openpype Env Vars and Tools Configuration Explained](https://community.ynput.io/t/openpype-env-vars-and-tools-configuration-explained/540)
+
+### How to publish lookdev from Houdini ? 
+
+Publishing and managing Lookdev in Houdini is within our plan.
+The current solution to publish materials is to use HDAs as you can publish most of Houdini nodes as HDA.
+
+### How to submit houdini patch version to deadline ?
+
+The custom AYON Deadline `GlobalJobPreLoad` functionality can help with that by adding the application specific environment variables before the job starts rendering. Using that we can point the Deadline Houdini plugin to e.g. just `houdini` for Deadline to find the executable by name instead of full path. To ensure it's found we just need to make sure the executable is available on the `PATH` environment variable. Like so:
+- update Houdini deadline config
+  ![faq-deadline-config](assets/houdini/admin/faq-deadline-config.png)
+- add Houdini dir to `PATH` environment variable and add `HOUDINI_VERSION` for each variant
+  ![faq-houdini-ayon-update-path](assets/houdini/admin/faq-houdini-ayon-update-path.png)
+
+### What template keys are available for use in Houdini settings?
+Because Ayon is in Beta stage. Please refer to the code [here](https://github.com/ynput/OpenPype/blob/c61a601c78669d70c472c67016eeb77531f42bab/openpype/pipeline/context_tools.py#L671-L692) to check the current available template keys
+