How Tos

Why?

The YoutTube GitLab channel has the Learn@GitLab playlist on it. This playlist is comprised of the videos the Developer Advocate team creates about the customer use cases which are the basis of our Use Case GTM. To increase the value we get from these videos it is valuable to cross reference to other videos, the playlist, and to subscribe, by adding appropriate CTA’s at the end of our videos.

Why

Automatically generating comparison infographics means that the grphic creation is data driven. The value of this is a few things:

• efficiency and quality - it is far more efficient and far less error prone to auto generate graphics than to have individuals hand creating each graphic
• scale - hand creation of each graphic does not scale. We are looking at generating over 80 different detailed images based on a lot of data, each one with over 106 touch points.
• iteration - as the infographic needs evolve being able to auto generate (and re-generate) the graphs means that we can iterate without heavy nearly as heavy a cost

Steps

1. Prep the data
   1. Raw Data
      1. Here’s the spreadsheet we are collecting the raw comparison analysis (GitLab viewable only)
      2. Data entry is being done on the Comparison DATA ENTRY Sheet tab. Please DO NOT add or delete columns to this sheet unless at the far right. Doing so will throw off all the other sheets.
      3. Once you’ve filled in the data on the DATA ENTRY tab, switch over to the FIGMA_DATA-Focus-Sync tab. This is the data represented for Figma consumption.
      4. For your entries you wish to graph, make sure that
         • there is logo image in the “Logo” row (3), and that the data in the cell is a URL that ends in either .png or .jpg. If it’s anything else then the plugin we are using will go into an endless read loop.
         • The “Competitor” row (2) has the proper name in it. This is the name as it will appear in the infographic. Make sure it has proper capitalization, spacing, etc. If you are doing a lot of them you can copy down from row 1, then run a title-case add-on, and find/replace to ditch “-“s’ and “_“s'.
      5. Your data is now ready to go. For each competitor you wish to generate a graph for, copy from the “Competitor” row (2) down to the end of the column of data (currently row 110), and then. . . .
   2. Staged data
      1. Create a copy of the file Infographic Autogen – Working File - Template.
      2. Make sure that your file is world readable. This is required for the plugin to work.
      3. Make a copy of the tab Template-EDIT A COPY (new tab name doesn’t matter, but I use “runX” and increment X).
      4. Make sure this tab is the first one in the list.
      5. Paste your copied competitor info into the new tab, in the following way:
         1. In the first empty column, place your curor in the “logo1” row (4).
         2. Right click => “Paste special” => “Paste values only”
      6. As a sanity check, the row “overview-percent” (6) should have a percentage pasted into it.
      7. Copy the competitor name into “Competitor1 - Competitor3” rows (1-3).
      8. Copy the logo URL into the “logo1” row (4) and “logo2” row (5).
2. Prep Figma
   1. Set up your template file
      1. You can create as many competitor infographs at once as youd like, you just need to make sure that your Figma file templates matches that number.
      2. Open the Figma file GitLab vs. Campaign - Infograph Creation Template - this is a read-only file
      3. Make a copy of the file into your local Figma workspace
      4. In this file, there are pages on the left. Right click on the page GitLab vs. Competitor Template, v2.
      5. Select to “Duplicate Page”.
      6. Immediately rename the new page so thing don’t get confusing. (I use “Run X” and increment X)
      7. On the new page
         1. Go to the lower left pane and find the object named “competitor-vs-gitlab”. Unlock it (icon on the right).
         2. Make as many copies of the whole infograph (the “competitor-vs-gitlab” object) as you need. hint there are two pre-setup templates (pages) you can start with instead, with 6 and 12 infographs)
      8. Your Figma file is ready to import into
   2. Install the plugin
      1. This all works via an amazing Figma plugin called Google Sheets Sync. <——– Click on this link from your browser session also logged into FIgma to install it into your Figma instance.
      2. That’s that. Not so hard huh?
3. Run the autogen
   1. Make sure in Figma you are showing the page you want to generate with
   2. Go to the Figma “hamburger” menu (top left, 3 parallel horizontal lines)
   3. Select “Plugins” => “Google Sheets Sync”
   4. In the dialog that pops up, where it says “Enter Sheets shareable link here”, paste the URL of your stage file (created earlier). reminder this file needs to be world readable.
   5. Set the pulldown selection to Update current selection only
   6. Click on the “Fetch & sync” button.
   7. Watch the magic happen . . .
   8. You might need to tweak the logo sizes and Competitor name a little in the header area, based on the input sizes of those items.
4. Get and use the results
   1. Export the resiults
      1. Once the infograph is generated, go back to the left pannel and change each object name (“competitor-vs-gitlab”) to reflect the competitor name on that infograph (click on it in the left pannel and see which infograph gets selected).
      2. Make sure nothing is selected (click on the background)
      3. Go to the “hamburger” menu
      4. Select “File” => “Export”
      5. In the box that pops up, select only the “competitor-vs-gitlab” images
      6. Click the “Export” button and save the file somewhere on your hard drive.
   2. Use the results
      1. Unzip the file to get the folder of all exported images
      2. The resulting images are too big for our comparison page purposes, so we’ll resize them
         1. On Mac, open a Terminal and go into the folder
         2. In the terminal run the command sips -Z 1081 *.jpg
         3. This will convert each file to 1081x1080 (LxW)
      3. Upload the images to wherever you need them to be used

Videos

• How this ends up working
• How to do it (above steps in video)

The magical Google Sheets Sync Figma plugin

• Plugin page
• Plugin documentation

Account info

We don’t currently have a shared AWS account for using AWS resources. For now, open an account with your personal credit card and expense it. You can start with a free trial. I will look into a team shared account.

Creating a cluster

There are many steps to set up a cluster in EKS, but there is a 3rd party script which I’ve found to be pretty good at orchestrating the work. It’s called eksctl. You’ll need this local to were you run the script from. There are also a set of utilities we created (just shell scripts) to lessen the pain of creating a cluster and configuring GitLab for a demo. Those can be found at https://gitlab.com/dangordon/eks-utils.git.

Creating and Publishing

This is the SSoT for the steps to creating and publishing video demos. These are designed to show up in our issue templates. There are several types of demo issue templates but this is what they have in common (with the exception of some specific publish locations details which need to be adjusted per issue template).

### Video should include
Tell one story across the whole video (have one key take away), what is being shown, why it matters to the audience, show it in action.

### Production
* [ ] Develop Demo Script - in partnership w/ PMM, PM, and other stakeholders
   * [Example 1](https://docs.google.com/document/d/1uICVyAqgKS2mAtvUaj4FZH0kUpeRO7v3qMV1f7YPDeg/edit?usp=sharing)
   * [Example 2](https://docs.google.com/document/d/1l3JUAAx6kLO4RxtuKapH5-eX_recVBDtGxIV5yj24KQ/edit) encourage collaboration.
* [ ] Configure demo scenario
* [ ] Record Demo

### Publishing
* [ ] Publish demo video to youtube **"GitLab"** channel, playlists: "Snapshots".
   * [ ] Add CTA's to the end of the new video and fix any other ones so the chain stays intact. See [adding CTA's to Learn videos](/handbook/marketing/developer-relations/technical-marketing/howto/add-ctas-to-learn-videos/) for more details.
   * [ ] Create attractive video thumbnails. See [thumbnail guide](https://louisem.com/198803/how-to-youtube-thumbnails) for more details.
* [ ] Publish demo video to GitLab Snapshots page at https://university.gitlab.com/.
* [ ] Add demo video to [GDrive Demo Folder](https://drive.google.com/drive/u/0/folders/1AWGh_v8Gn26RYhPYmc4jWor-RgqvngRZ) in the appropriate folder.
* [ ] Announce new video (with link) to Slack channel #marketing

Issue Templates the above is used in

• Feature Demo
• Use Case Differentiator Demo
• Use Case Market Requirement Demo
• Use Case Overview Demo

1. Upload a video

1. There are two YouTube channels we use at GitLab:

   • Branded: used for official content intended for people in the wider community. This content must be approved by the Brand team.
   • Unfiltered: used for content intended for team and community members. This content does not require approval from the Brand team but still should follow all brand guidelines and use up-to-date brand assets.

   Contact the Brand team in the #brand_video Slack channel for any questions.