Style guides
Introduction
Syle Guides are central in Assetflw and serves many purposes, not just providing information to the photographer. Style Guides are attached to products in the Work Order so that each product will have one Style Guide with One or more views. The Style Guide in Asetflw serves three central purposes:
- Give information to the photographer on what to shoot and how
- Define how to identify images when they are uploaded
- Set the rules for naming you assets.
The Style Guide in Assetflw is structured with some core information about the specific Style and then all the views that are included in the Style Guide, e.g. Front, Left, Back, etc.
Give information to the photographer
It is important that the photographer knows what to shoot and how to shoot it. This might not appear to be so important if you always shoot the same angles and the same nr of images. However, it becomes more and more important to be able to define different styles for different purposes. It is therefore important that the photographer and or the Stylist has the right information at all the shooting occetions.
In the Style Guide in Assetflw you specify:
- The name for the Style Guide
- A description for the Style Guide
- In what angles you wish to shoot your products
- What type of Style Guide you define, e.g. Model, Flatlay, etc.
- Som detailed data about the view such as padding, background etc.
You may also add an image to theStyle Guide, this can be done per Style Guide and per view defined in each Style Guide
Style guide types
Style gude types area set of pre defined types of style guides that supports identifying assets later in the workflow. The typical example may be if you want to separate model images from flatlay images it may be done via style guide types. The Style guide types are defined under advanced settings, please select “Settings/Advanced” to identify and define your specific types.
How to identify images when uploading
In each view of a Style Guide you have some very important fields to define, one of the being the Upload identifier. This part will allow you to define a pattern that can be used to identify what view the image belongs to.
Example: You set a suffix 1 to all your front images when shooting them. Then, by setting the Upload identifier value to “1” for your front view will tell the upload procedure that this asset belongs to the front view.
NOTE: you still need to have some other way to identify that the image belongs to a specific product, e.g. use EAN code to identify the product and the Upload identifier to find the view.
Asset naming identity
Just because you set “1” as a suffix in the photo shoot doesn’t necessarily mean that you want the Asset to be named “1”.
The whole idea is that it should be very easy to work with naming when shooting even though it could be very complex naming requirements.
Example: You identify the view by the suffix “1” for fron view but you might want the fron view to be named with the suffix “fv-1”, e.g. you upload an image using “ean-code_1” and want to name it “ean-code_fv-1”.
Of course you can rename the ean-code as well but that is not part of the style guide, see instead section on identifying and renaming images automatically.
