Scope

The idea of publishing is typically deeply nested in surrounding production concerns. The idea with Pyblish is to try and isolate one concern that a can peacefully co-exist with external elements; i.e. Quality Assurance.

Target audience

Pyblish is targeted at small development teams looking for faster and higher quality throughput and large development teams looking for alternatives to an existing pipeline in open source quality assurance for content.

Industries:

• Commercials
• Games
• Film
• Visualisation

See also

• Style

Illustration

Below is an illustration of where, within a creation >> export process, Pyblish fits in.

            |
            | Create content
            |
            v
         __ # ------------------------------------------------------
        |   |
        |   | Validate
        |   | # Before any data can be shared, it must be validated.
        |   | # It may be valid when, say, it doesn't exceed 3
        |   | # meters in height.
        |   v
Pyblish |   # ------------------------------------------------------
        |   |
        |   | Save files
        |   | # Once validated, data is extracted and saved relative
        |   | # your working file.
        |   | # E.g. /workspace/pyblished/140801_1458_1312
        |   |
        |   v
        |   # ------------------------------------------------------
        |__ |
            | Organise files
            | # From here, you are expected to properly organise
            | # your files.
            | # E.g. /project/spiderman/assets/Peter/pyblished/v001
            |
            v

Next: Requirements >>