ayon-core/website/docs/admin_anatomy.md

id	title	sidebar_label
admin_anatomy	Project Anatomy	Folder Structure

PROJECT Structure

This is example project structure when using Pype:

Project
  ├───assets
  │   ├───Bob
  │   └───...
  └───episodes
      └───ep01
          └───sq01
              └───ep01_sq01_sh001
                  ├───publish
                  └───work

:::note Shot naming We do strongly recommend to name shots with their full hierarchical name. Avalon doesn't allow two assets with same name in project. Therefor if you have for example:

sequence01 / shot001

and then

sequence02 / shot001

you'll run into trouble because there are now two shot001.

Better way is to use full qualified name for shot. So the above become:

sequence01 / sequence01_shot001

This has two advantages: there will be no duplicities this way and artists can see just by looking at filename the whole hierarchy. :::

ASSET Structure

Bob
  ├───publish
  │   ├───model
  │   │   ├───modelMain
  │   │   ├───modelProxy
  │   │   └───modelSculpt
  │   ├───workfile
  │   │   └───taskName
  │   ├───rig
  │   │   └───rigMain
  │   ├───look
  │   │   ├───lookMain
  │   │   │   └───v01
  │   │   │       └───texture
  │   │   └───lookWet
  │   ├───camera
  │   │   ├───camMain
  │   │   └───camLayout
  │   ├───cache
  │   │   ├───cacheChar01
  │   │   └───cacheRock01
  │   ├───vrproxy
  │   ├───fx
  │   └───setdress
  └───work
      ├───concept
      ├───fur
      ├───modelling
      ├───rig
      ├───look
      └───taskName