All assets for ads should now be located in a common, organized team Google Cloud bucket. We should, as best as possible, organize these assets by client or jira ticket number.
The Google Bucket for all CreativeTech assets is located here: nyt-ads-static-assets/ads/tbrandcreativetech
The Bucket
This bucket is divided into three sections:
flex-frames
/####_ClientName
/ClientName
/lib
paid-posts
/####_ClientName
/ClientName
/lib
images
/####_ClientName
ClientName
Rules
LIBRARIES: For paid posts and flex frames, there is a /lib folder. All generic externalized scripts should be put in here. If you have libraries that are part of a project, please keep them in that project folder.
EXAMPLE: The ad-tracking.js software we use for all flex frames should be stored in the /flex-frames/lib folder.
FLEX-FRAME/PAID-POST SUBFOLDERS: When storing assets for these type of projects, try and pre-prepend the ClientName with the Jira ticket number. This way there’s a way to reference the type of assets in a folder. If this cannot be done or you require a more generic name, please use the client name option.
IMAGES: If you’re just storing images, use this folder. As above, try and use a Jira ticket number when creating a folder name. If you think you’ll be using an image more that one time, feel free to use the more generic client name.
Notes
When to use store assets in the /flex-frame vs. /images folder. Use the flex-frame folder when you are doing custom work that requires multiple types of assets, like .js, .css and image files. If it’s just images, use the /images folder.
You do not need to move assets that are already in previously defined locations. This is a roll-forward process.