Skip to content
Gallery
nytgames
CreativeTech Wiki (internal)
creativeTECH Wiki
Share
Explore
Recipes

icon picker
Upload files to the Creative Tech Bucket

Features

This is a step by step recommendation on how to upload files to the Creative Tech bucket, for example to avoid the Webflow compression.

How to

1) Optimise the assets

Prepare and
optimise the assets
⁠
for web use.

2) Add a new folder

This is the folder where we save the assets used in paid posts or ad units.
⁠
https://console.cloud.google.com/storage/browser/nyt-ads-static-assets/ads/creative-tech
⁠
⁠
Please add your files in the proper subfolder (”paid-posts” or “flex-frames”) in a folder with a significant name, following the convention used. Prefix your folder with the Jira ticket number or the year of the program, plus the client or project name.
Most likely, files on the GC bucket will stay online for a long time and it’s important to be tidy and avoid confusion.
⁠
Screenshot 2024-04-03 at 11.33.41.png
⁠
⁠

3) Upload the files

Just drag and drop the files in your folder.

4) Modify the base URLs

In the object details tab you’ll find a public URL for the assets. Modify its base URL to leverage our Fastly capabilities.
Example, from this:
https://storage.cloud.google.com/nyt-ads-static-assets/ads/creative-tech/paid-posts/2024-gsk-videos-scrub/20240403/compressed-mp4/1.mp4
You want to have this:
https://static01.nytimes.com/ads/creative-tech/paid-posts/2024-gsk-videos-scrub/20240403/compressed-mp4/1.mp4

5) (Optional) Test the URLs

You might find yourself working with long lists of assets. In this case, you can work with your terminal (ls -1 . will list the files in the folder in a single column) and the multi-line editing capabilities of your editor (
VS Code
⁠
, for example) to create a handy list of URLs.
Once done, you can test the URLs with a script similar to the following.
#!/bin/bash

# ANSI color codes
RED="\033[0;31m"
GREEN="\033[0;32m"
NC="\033[0m" # No Color

# List of URLs to check
urls=(
"https://static01.nytimes.com/ads/creative-tech/paid-posts/2024-gsk-videos-scrub/20240403/compressed-jpegs/1.jpg"
"https://static01.nytimes.com/ads/creative-tech/paid-posts/2024-gsk-videos-scrub/20240403/compressed-jpegs/10.1920.jpg"
# Add more URLs to check here...
)

# Initialize an empty array to keep track of not found URLs
not_found_urls=()

for url in "${urls[@]}"; do
status=$(curl -o /dev/null -s -w "%{http_code}\n" "$url")
if [ "$status" -eq 404 ]; then
echo -e "${RED}$url is not accessible (404).${NC}"
not_found_urls+=("$url") # Add the URL to the list of not found URLs
else
echo -e "${GREEN}$url is accessible (Status: $status).${NC}"
fi
done

# Check if there are any not found URLs and list them
if [ ${#not_found_urls[@]} -ne 0 ]; then
echo -e "${RED}The following URLs were not found:${NC}"
for url in "${not_found_urls[@]}"; do
echo -e "${RED}$url${NC}"
done
fi


Features
How to
1) Optimise the assets
2) Add a new folder
3) Upload the files
4) Modify the base URLs
5) (Optional) Test the URLs
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.