diff --git a/website/docs/artist_hosts_nuke_tut.md b/website/docs/artist_hosts_nuke_tut.md
index 0ec1e104b9..4d116bd958 100644
--- a/website/docs/artist_hosts_nuke_tut.md
+++ b/website/docs/artist_hosts_nuke_tut.md
@@ -1,12 +1,150 @@
---
id: artist_hosts_nuke_tut
-title: Nuke QuickStart
-sidebar_label: Nuke QuickStart
+title: Nuke
+sidebar_label: Nuke
---
-This QuickStart is just a small introduction to what OpenPype can do for you. It attempts to make an overview for compositing artists, and simplifies processes that are better described in specific parts of the documentation.
+:::note
+OpenPype supports Nuke version **`11.0`** and above.
+:::
-## Launch Nuke - Shot and Task Context
+## OpenPype global tools
+
+- [Set Context](artist_tools.md#set-context)
+- [Work Files](artist_tools.md#workfiles)
+- [Create](artist_tools.md#creator)
+- [Load](artist_tools.md#loader)
+- [Manage (Inventory)](artist_tools.md#inventory)
+- [Publish](artist_tools.md#publisher)
+- [Library Loader](artist_tools.md#library-loader)
+
+## Nuke specific tools
+
+
+
+
+### Set Frame Ranges
+
+Use this feature in case you are not sure the frame range is correct.
+
+##### Result
+
+- setting Frame Range in script settings
+- setting Frame Range in viewers (timeline)
+
+
+
+
+
+
+
+
+
+
+1. limiting to Frame Range without handles
+2. **Input** handle on start
+3. **Output** handle on end
+
+
+
+
+### Set Resolution
+
+
+
+
+
+This menu item will set correct resolution format for you defined by your production.
+
+##### Result
+
+- creates new item in formats with project name
+- sets the new format as used
+
+
+
+This menu item will set correct Colorspace definitions for you. All has to be configured by your production (Project coordinator).
+
+##### Result
+
+- set Colorspace in your script settings
+- set preview LUT to your viewers
+- set correct colorspace to all discovered Read nodes (following expression set in settings)
+
+
+
+It is usually enough if you once per while use this option just to make yourself sure the workfile is having set correct properties.
+
+##### Result
+
+- set Frame Ranges
+- set Colorspace
+- set Resolution
+
+
+
+
+
+
+
+
+
+### Build Workfile
+
+
+
+
+This tool will append all available subsets into an actual node graph. It will look into database and get all last [versions](artist_concepts.md#version) of available [subsets](artist_concepts.md#subset).
+
+
+##### Result
+
+- adds all last versions of subsets (rendered image sequences) as read nodes
+- ~~adds publishable write node as `renderMain` subset~~
+
+
+
+
+
+
+
+
+
+## Nuke QuickStart
+
+This QuickStart is short introduction to what OpenPype can do for you. It attempts to make an overview for compositing artists, and simplifies processes that are better described in specific parts of the documentation.
+
+### Launch Nuke - Shot and Task Context
OpenPype has to know what shot and task you are working on. You need to run Nuke in context of the task, using Ftrack Action or OpenPype Launcher to select the task and run Nuke.
@@ -16,24 +154,27 @@ OpenPype has to know what shot and task you are working on. You need to run Nuke
You can [configure](admin_settings_project_anatomy.md#Attributes) which DCC version(s) will be available for current project in **Studio Settings → Project → Anatomy → Attributes → Applications**
:::
-## Nuke OpenPype menu shows the current context
+### Nuke Initial setup
+Nuke OpenPype menu shows the current context
Launching Nuke with context stops your timer, and starts the clock on the shot and task you picked.
-## Nuke Initial setup
Openpype makes initial setup for your Nuke script. It is the same as running [Apply All Settings](artist_hosts_nuke.md#apply-all-settings) from the OpenPype menu.
-Reads frame range and resolution from Avalon database, sets it in Nuke Project Settings,
+- Reads frame range and resolution from Avalon database, sets it in Nuke Project Settings,
Creates Viewer node, sets it’s range and indicates handles by In and Out points.
-Reads Color settings from the project configuration, and sets it in Nuke Project Settings and Viewer.
+- Reads Color settings from the project configuration, and sets it in Nuke Project Settings and Viewer.
-Sets project directory in the Nuke Project Settings to the Nuke Script Directory
+- Sets project directory in the Nuke Project Settings to the Nuke Script Directory
+:::tip Tip - Project Settings
+After Nuke starts it will automatically **Apply All Settings** for you. If you are sure the settings are wrong just contact your supervisor and he will set them correctly for you in project database.
+:::
-## Save Nuke script – the Work File
+### Save Nuke script – the Work File
Use OpenPype - Work files menu to create a new Nuke script. Openpype offers you the preconfigured naming.
@@ -58,7 +199,7 @@ More about [workfiles](artist_tools#workfiles).
- [Color setting](project_settings/settings_project_nuke) for Nuke can be found in **Studio Settings → Project → Anatomy → Color Management and Output Formats → Nuke**
:::
-## Load plate – Asset Loader
+### Load plate
Use Load from OpenPype menu to load any plates or renders available.
@@ -71,7 +212,7 @@ Note that the Read node created by OpenPype is green. Green color indicates the
More about [Asset loader](artist_tools#loader).
-## Create Write Node – Instance Creator
+### Create Write Node
To create OpenPype managed Write node, select the Read node you just created, from OpenPype menu, pick Create.
In the Instance Creator, pick Create Write Render, and Create.
@@ -85,7 +226,7 @@ This will create a Group with a Write node inside.
You can configure write node parameters in **Studio Settings → Project → Anatomy → Color Management and Output Formats → Nuke → Nodes**
:::
-## What Nuke Publish Does
+#### What Nuke Publish Does
From Artist perspective, Nuke publish gathers all the stuff found in the Nuke script with Publish checkbox set to on, exports stuff and raises the Nuke script (workfile) version.
The Pyblish dialog shows the progress of the process.
@@ -96,7 +237,7 @@ The left column of the dialog shows what will be published. Typically it is one
The right column shows the publish steps
-#### Publish steps
+##### Publish steps
1. Gathers all the stuff found in the Nuke script with Publish checkbox set to on
2. Collects all the info (from the script, database…)
3. Validates components to be published (checks render range and resolution...)
@@ -110,12 +251,12 @@ The right column shows the publish steps
Gathering all the info and validating usually takes just a few seconds. Creating reviews for long, high resolution shots can however take significant amount of time when publishing locally.
-#### Pyblish Note and Intent
+##### Pyblish Note and Intent
Artist can add Note and Intent before firing the publish button. The Note and Intent is ment for easy communication between artist and supervisor. After publish, Note and Intent can be seen in Ftrack notes.
-#### Pyblish Checkbox
+##### Pyblish Checkbox
@@ -129,7 +270,7 @@ More info about [Using Pyblish](artist_tools#publisher)
You can configure Nuke validators like Output Resolution in **Studio Settings → Project → Nuke → Publish plugins**
:::
-## Review
+### Review
When you turn the review checkbox on in your OpenPype write node, here is what happens:
@@ -152,7 +293,7 @@ You can configure reviewsin **Studio Settings → Project → Global → Publish
Reviews can be configured separately for each host, task, or family. For example Maya can produce different review to Nuke, animation task can have different burnin then modelling, and plate can have different review then model.
:::
-## Render and Publish
+### Render and Publish
@@ -164,17 +305,17 @@ If you want to render and publish on the farm in one go, run publish with On far
-## Version-less Render
+### Version-less Render
-OpenPype is configured so your render file names have no version number. The main advantage is that you can keep the render from the previous version and re-render only part of the shot. With care, this is handy.
+OpenPype is configured so your render file names have no version number until the render is fully finished and published. The main advantage is that you can keep the render from the previous version and re-render only part of the shot. With care, this is handy.
Main disadvantage of this approach is that you can render only one version of your shot at one time. Otherwise you risk to partially overwrite your shot render before publishing copies and renames the rendered files to the properly versioned publish folder.
When making quick farm publishes, like making two versions with different color correction, care must be taken to let the first job (first version) completely finish before the second version starts rendering.
-## Managing Versions
+### Managing Versions
@@ -182,14 +323,15 @@ OpenPype checks all the assets loaded to Nuke on script open. All out of date as
Use Manage to switch versions for loaded assets.
+## Troubleshooting
-## Fixing Validate Containers
+### Fixing Validate Containers
If your Pyblish dialog fails on Validate Containers, you might have an old asset loaded. Use OpenPype - Manage... to switch the asset(s) to the latest version.
-## Fixing Validate Version
+### Fixing Validate Version
If your Pyblish dialog fails on Validate Version, you might be trying to publish already published version. Rise your version in the OpenPype WorkFiles SaveAs.
Or maybe you accidentaly copied write node from different shot to your current one. Check the write publishes on the left side of the Pyblish dialog. Typically you publish only one write. Locate and delete the stray write from other shot.
\ No newline at end of file
diff --git a/website/sidebars.js b/website/sidebars.js
index f805382518..23de72001b 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -18,7 +18,6 @@ module.exports = {
label: "Integrations",
items: [
"artist_hosts_hiero",
- "artist_hosts_nuke",
"artist_hosts_nuke_tut",
"artist_hosts_maya",
"artist_hosts_blender",