ready for prod 2024

Dockerfile

@@ -2,6 +2,9 @@ FROM node:lts-alpine AS build
 WORKDIR /home/
 RUN mkdir -p /home/build
 COPY package.json yarn.lock ./
+
+RUN apk add --no-cache autoconf
+
 RUN yarn
 COPY . .
 RUN yarn build

docs/user/basic-concepts/actions/conform.md

@@ -3,7 +3,7 @@ id: conform
 title: Conform
 sidebar_position: 10
 ---
-To conform = Include your scenes and assets in the pipeline.
+To conform = Include your scenes and assets in the pipeline. This action rename you file and put it in the right folder. **It does not run any quality checks or check dependencies.**
 ## In Silex
 ![](../../../../static/img/user_guide/home_page/home_interface_conform.png)
 Conform button is in the home page.

docs/user/basic-concepts/actions/import.md

@@ -0,0 +1,33 @@
+---
+id: import
+title: Import/Reference
+sidebar_position: 30
+---
+This action lets you import publish into your scenes. Instead of going to the server and importing your files by hand, you simply tell silex which task you want to import.
+
+## In Houdini
+![](../../../../static/img/user_guide/actions/houdini_shelf/houdini_silex_shelf_import.png)                         
+From your houdini work file, simply go to the silex shelf and click on the import button.
+At this moment you can import as :
+- Geometry
+- Alembic scene
+- Arnold Procedural
+- Arnold Volume
+Send a [ticket](../../interface/tickets.md) to the TD Gang if you need another type of import.
+
+![](../../../../static/img/user_guide/actions/import/import_in_houdini.gif)             
+Choose the file you want to import.
+If it is a image sequence, keep activate the toggle **Files sequence**.
+**Import as** allows you to choose the import type. In this example I import .begeo.sc so I keep *Geometry*.
+![](../../../../static/img/user_guide/actions/import/imported_in_houdini.png)
+My image sequence was successfully imported.
+
+
+## In Maya
+![](../../../../static/img/user_guide/actions/maya_shelf/maya_silex_shelf_import.png)                       
+From your maya work file, you can find the import button and the reference button.                  
+To exploit the power of the pipeline to its full potential, import as a reference rather than importing at all.
+
+![](../../../../static/img/user_guide/actions/import/import_in_maya.gif)                           
+Choose the file you want to import.                 
+We recommend that you choose a namespace.  

docs/user/basic-concepts/actions/publish.md

@@ -1,7 +1,7 @@
 ---
 id: publish
 title: Publish
-sidebar_position: 30
+sidebar_position: 40
 ---
 **Publish** is the action of sending a version of your files to a shared space. Basicaly, it's **exporting files for the next step in the pipeline.**
 In fact, it's not your work files that will be shared, but a copy or export of them that will be saved on the network.

docs/user/basic-concepts/workflow/change_task.md

@@ -0,0 +1,22 @@
+---
+id: change_task
+title: Convert working scene to another task
+sidebar_position: 20
+---
+# Convert scene to another task
+
+Situation : You are a FX artist, you have done an FX for the shot s01p010 but you wan to use it as a base for your s01p020 shot.
+
+1 : Open your s01p010 FX scene.             
+
+2 : [Save](../actions/save.md) your scene **and** increment save your scene. Your scene name must be the name of your initial scene (in our example, s01p010 fx).               
+![](../../../../static/img/user_guide/workflow/switch_task/wflw_initial_name.png)
+
+3 : 
+![](../../../../static/img/user_guide/actions/houdini_shelf/houdini_silex_shelf_switch.PNG)
+Use the tool switch task!
+![](../../../../static/img/user_guide/workflow/switch_task/switch_task_action.gif)      
+The tool ask you to wich task you want to convert your current scene. In my example, I select the s01p020 FX task.
+
+4 : Finally, [save](../actions/save.md) again with the silex save tool. Now, your scene is set for another task, at the right place in the pipeline.
+![](../../../../static/img/user_guide/workflow/switch_task/wflw_final_name.png)

docs/user/basic-concepts/workflow/create_new_scene.md

@@ -0,0 +1,16 @@
+---
+id: create_new_scene
+title: Create a new working scene
+sidebar_position: 10
+---
+# Create a new scene
+
+Situation : You are an animator and you have to start to animate a shot.
+
+1 :
+![](../../../../static/img/user_guide/workflow/tutorial/workflow_create_new_scene01.gif)
+First, go to your shot in the [file explorer](../../interface/file-explorer.md) and click on the task animation. To open a new scene, you just have to click on a software in the area next to the workable button.
+
+2 : When your scene is open, you can save it at the right place by using the [save tools](../actions/save.md).
+
+3 : Now, you just have to import as reference your rig and the other assets you need by using the [import/reference tools](../actions/import.md).

docs/user/basic-concepts/workflow/workflow.md

@@ -0,0 +1,64 @@
+---
+id: workflow
+title: Workflow
+sidebar_position: 30
+---
+
+## publish / work
+
+### What is a Work folder ? :
+
+The Work folder is accessible from the interface as you can see [here](../../interface/file-explorer.md)
+This is a free space for you to save scenes in progress. It's a folder that is not backuped on the server, and only exists in your computer. This is where you save your scene and incremented versions.
+
+### A pick in the Publish folder :
+
+The **Publish** is probably the most important concept to grasp in a pipeline. When a scene is published, it means the scene is "finished", or in it's "final version" and ready for the next stage in the pipeline. This goes for every departement, but a published file is a little bit more than that and if we want to understand what it really is, we need more knowledge on how it works.
+
+This is important knowledge to have, and will be useful for other concepts and services on Silex or in other pipelines. So read carefully 👀.
+
+You see, working in a pipeline usually means, **working with a server**. To keep it simple, I'll go straight to the point and try to avoid unnecessary details. In Silex, we use a server "connected"" to every computer in school ( there are actually 2 servers + one data center, but for the sake of this explaination, let's say there is only one ok ? :) ). Since the server is accessible by every computers in Artfx (drive letters I and O.), every files stored in it can be accessed from **anywhere** 🌍
+
+When you put a file in a **publish** folder, this folder is synchronised on the server and can be accessed by any computer. Got it ? So this also means that the [renderfarm](../../renderfarm/renderfarm.md) knows where the file is and can render it in the case of Maya scene, Houdini scene, vrscene ...
+
+( I encourage reading the documentation on the [renderfarm](../../renderfarm/renderfarm.md) for more details. )
+
+FURTHERMORE ! To be able to render a scene on the [renderfarm](../../renderfarm/renderfarm.md), we also need every textures or references to be accessible on the server. This is the tricky part, and the [publish tool](../actions/publish.md) ensures that every files linked, in any way, to the published file is also copied on the server. That's a second important aspect of the **Publish**.
+
+:::note
+<u>So, to summerize :</u>
+
+- A published file (a file exported to the publish folder by Silex's [publish tool](../actions/publish.md)) is accessible **anywhere** as well as it's references, textures, etc... .
+
+- A published file is only the finale version of your work.
+
+(there will be a full, step by step, example later.)
+:::
+
+## Context and Tasks
+
+Another important concept in Silex is the concept of **task** and **context**.
+
+![](/img/user_guide/workflow/workflow_tasks.png)
+
+Here in this picture, we just clicked on the shot 030 (as you can see in the red). Inside you can see all the different **tasks** assigned to this shot. (**Tasks** are the equivalent of departements in a vfx/3D studio 🦉)
+
+For exemple : Layout, lookdev...
+
+You can add a new custom task to the list by clicking on the "+" button near the shot name. Then fill in the pop up window :
+
+![](/img/user_guide/workflow/workflow_custom_task.png)
+
+:::caution
+The list of tasks is defined by the supervisors before the project begins. If you add a task through silex, it will not appear in shotgrid. Ask to the TD Gang if you can add a task beofre.
+:::
+
+Now, let's say you are a layout artist. After selecting your Shot or Asset in the explorer, you can select the task **Layout**, and [open a new scene](../../interface/file-explorer.md) from the launch window. the new scene is now open in a **Context** specific to this task. this means that the [tools in the Silex shelf](../actions/actions.md) will take into acount that your are in a layout scene in for the shot you selected. In other terms, Silex KNOWS where you are, and will use it for publishing files.
+
+As mentioned before, the [publish tool](../actions/publish.md) exports the scene or the selection into a publish folder. Since you work in a **Layout** scene, if you use the [publish tool](../actions/publish.md), the exported files will be accessible in the publish folder. You will be able to access it ONLY in this particular task, in this particular shot.
+
+(To see published files, se the related section in [Browsing through files](../../interface/interface.md))
+
+## workflow exemple step by step :
+
+Before getting into it, you need to read the documentation on the [interface](../../interface/interface.md) and the [file explorer](../../interface/file-explorer.md)

docs/user/kitsu/create_account.md

@@ -0,0 +1,11 @@
+---
+id: create_account
+title: Create your silex Account
+sidebar_position: 10
+---
+![](../../../static/img/user_guide/kitsu/kitsu_login.png)
+
+If you've never logged in to kitsu before, your login is your artfx address and your password is ***default***. Then, kitsu will ask you to create your password.
+Please write down your password somewhere. It's very difficult to recover a kitsu account if you forget your password.
+
+When it's done, you can connect to silex using your kitsu account.

docs/user/kitsu/kitsu.md

@@ -0,0 +1,14 @@
+---
+id: kitsu
+title: Kitsu
+sidebar_position: 40
+---
+Kitsu is the silex database. This is where your silex account is created, and your shots/assets info stored.
+You can find it at this url : (http://kitsu.prod.silex.artfx.fr/)               
+
+**DON'T TOUCH ANYTHING IN IT EXPECT FOR THIS ACTION**:
+- Create your silex account
+- Change your tasks thumbnail
+- Change your profil picture
+
+For any other needs, please ask the TD Gang before.

docs/user/kitsu/profile_picture.md

@@ -0,0 +1,8 @@
+---
+id: profile_picture
+title: Change your profile picture
+sidebar_position: 20
+---
+Simply go to your profile when you are log in http://kitsu.prod.silex.artfx.fr. Then clic on **Change avatar** button.
+![](../../../static/img/user_guide/kitsu/kitsu_profile_picture.gif)
+![](../../../static/img/user_guide/kitsu/kitsu_change_avatar.png)

docs/user/kitsu/task_thumbnail.md

@@ -0,0 +1,24 @@
+---
+id: task_thumbnail
+title: Change tasks thumbnail
+sidebar_position: 30
+---
+In Silex, thumbnail are automatically generate by the action [publish](../basic-concepts/actions/publish.md).
+![](../../../static/img/user_guide/kitsu/silex_thumbnail_prev.png)
+But, at the beginning, when you've never published before, your [file explorer](../interface/file-explorer.md) will be filled with gray squares. If you'd like to find your way around better and post your own thumbnails, here's how:
+
+1 : Go to your [kitsu](kitsu.md) account.
+
+![](../../../static/img/user_guide/kitsu/kitsu_change_thumbnail.gif)
+
+2 : In the file explorer, go to the asset or shot you want to add a thumbnail. 
+
+3 : Click on the task where you want to add a thumbnail.
+
+4 : Click on the **add a preview to publish** button and select your image.
+
+5 : Finally, to publish it, click on the **Set this preview as thumbnail** button (see screenshot under).
+![](../../../static/img/user_guide/kitsu/kitsu_set_thumbnail.png)
+
+Voila! A thumbnail has been added to your shot or asset!
+![](../../../static/img/user_guide/kitsu/silex_thumbnail_final.png)

docs/user/renderfarm/renderfarm.md

@@ -1,5 +1,7 @@
 ---
 id: renderfarm
 title: Renderfarm
-sidebar_position: 40
+sidebar_position: 50
 ---
+
+soon