GitLab Commit Virtual is here. Register Now for our 24 hour immersive DevOps experience.
Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Gated Content

Overview

This page focuses on gated content as an offer for our marketing channels and integrated campaigns, including in-house created content, analyst relations content, and downloadable competitive content. If you have any questions about content planning, please visit the Global Content handbook page, and with questions about the process of tracking and landing page creation below, please post in the #marketing_programs Slack channel.

Types of Content Programs

Gating Criteria

Gated Not Gated
Whitepapers Blogs
eBooks Infographics
Reports Technical Training Resources
On-Demand Webcasts Customer Testimonials
Comparison PDFs Case Studies

Note: if a new type of gated content needs to be introduced, and it is expected that it will be a regularly created piece of content (for example, as we begin to roll out Comparison PDFs), please post in [#marketing_programs slack channel(https://gitlab.slack.com/archives/CCWUCP4MS) to determine if steps need to be taken with Marketing Ops and Sales Ops for automation and reporting.

Internal Content (created by the GitLab team)

Alignment to Campaigns: All gated content should be aligned to a content pillar (owned by Content Marketing) and a primary integrated campaign (owned by Marketing Programs). If no active or planned campaign is aligned, a campaign brief (including audience data) must be created for use by Digital Marketing Programs. There should be a clear reason why we are moving forward with content that doesn't align to an integrated campaign.

Reporting: when someone submits a form on the gated content landing page, an online bizibe touchpoint is created containing rich utm parameters. The campaign landing page often uses different language aligned to the integrated campaign messaging.

Organizing content pillar epics and issues

🏷️ Label statuses:

  1. Content Pillar Epic: Content DRI creates content pillar epic
  2. Content Asset Epics: Content DRI creates content asset epics (using code below) and associates to pillar epic
  3. Related Issues: Content DRI creates the issues as designated in the epic code, and associates to the content asset epic

View the workback timeline calculator here

> NAME EPIC: *[type] Name of Asset* (ex. [eBook] A beginner's guide to GitOps)

> START DATE = date epic opened, DUE DATE = launch date

<!-- DELETE THIS LINE AND ABOVE ONCE EPIC EDITED -->

## Launch date: 

## [Live landing page link]() - `to be added when live`

#### :key: Key Details
* **Content Marketing:**  
* **Marketing Programs:** 
* **Product Marketing:** 
* **Official Content Name:** 
* **Official Content Type:** 
* [ ] [main salesforce program]()
* [ ] [main marketo campaign]()

## :memo: Documents to Reference
* [asset copy draft]() - `doc to be added by Content Marketing`
* *phase out?* [landing page copy]() - `doc to be added by Content Marketing` ([clone the template here](https://docs.google.com/document/d/1xHnLKPCaXrpEe1ccRh_7-IqgNbAlzQsZVc-wr1W4ng8/edit#))
* [creative requirements]() - `Content DRI to link to new tab on relevant use case creative googledoc` - [handbook for more info]()
* [creative final]() - `Design DRI to link to repo in GitLab`

### :books: Issues to Create
<details>
<summary>Expand below for quick links to issues to be created and linked to the epic.</summary>

[Use the workback timeline calculator to assign correct due dates based off of launch date](https://docs.google.com/spreadsheets/d/1dKVIZGbbOLoR5BdCqXqCQ40qJlQNif9waTiHc8yWggQ/edit#gid=1648326617)

* [ ] Prep: [Asset Copy Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/-/issues/new?issuable_template=content-resource-request) - Content
* [ ] Prep: [Landing Page Copy Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=marketo-landing-page-copy) - Content
* [ ] Prep: [Asset Design Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/-/issues/new?issuable_template=design-request-content-resource)
* [ ] Prep: [Digital Design Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/-/issues/new?issuable_template=) - Design `need issue temlpate`
* [ ] Develop: [Pathfactory Track Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=pathfactory_request)
* [ ] Develop: [Marketo Landing Page & Automation Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-creation)
* [ ] Activate: [Resource Page Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=resource-page-addition)
* [ ] Activate: [Digital Marketing Promotion Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=mktg-promotion-template)
* [ ] Activate: [Organic Social Issue](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/issues/new?issuable_template=social-general-request)
* [ ] Activate: [Website Merchandising Issue]() - Content `need issue template`
* [ ] Activate: [Blog Merchandising Issue]() - Content `need issue template`
* [ ] Activate: [Homepage Feature (only when applicable)](https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/new?issuable_template=request-website-homepage-promotion)
</details>

/label ~"Content Marketing" ~"Gated Content" ~"Marketing Programs" ~"mktg-status::plan"

Analyst Content (delivered by analysts)

When Analyst Relations determines that they will be purchasing analyst content to be gated, they are responsible for creating the epics and associated issues to request work of all relevant teams (outlined below to try to make it efficient, comprehensive, and repeatable!).

If the analyst content is thought leadership (i.e. a whitepaper or non-competitor comparison report), it should be planned in advance of purchase with at least a 30 business day time to launch date. This allows time to plan activation into existing and future integrated campaigns and content pillars.

View the workback timeline calculator here

Organizing analyst content epics and issues

🏷️ Label statuses:

  1. Analyst Relations Asset Epic: Analyst Relations DRI creates epic (using code below)
  2. Related Issues: Analyst Relations DRI creates the issues as designated in the epic code, and associates to the analyst relations asset epic

Please note that if details and landing page copy are not provided, the MPM is blocked and will not be able to gate the resource.

> NAME EPIC: *[type] Name Exactly as Appears On Report* (ex. [report] 2020 Gartner MQ for Application Security Testing (AST))

> START DATE = date epic opened, DUE DATE = launch date

<!-- DELETE THIS LINE AND ABOVE ONCE EPIC EDITED -->

## Launch date: 

## Live Pages: [/analyst/ commentary page]() and [download page]() - `to be added when live`

#### :key: Key Details
* **Analyst Relations:** 
* **Product Marketing:** 
* **Marketing Programs:** 
* **Content Marketing:** 
* **Official Content Name:** 
* **Official Content Type:** 
* **Validity / Expiration Date (if relevant):** (start date - end date)
* [ ] [main salesforce program]()
* [ ] [main marketo campaign]()

## :traffic_light: Green light?

:white_check_mark: *If the decision is made to purchase the report, AR opens the below documents and issues to request work from the relevant teams to execute toward launch.**

:no_entry: *If the decision is made **not** to purchase the report, AR closes out the epic.*

## :memo: Documents to Reference
* [content draft]() - `link to temporary unlicensed version when available`
* [landing page copy]() - `doc to be added by Analyst Relations` ([clone the template here](https://docs.google.com/document/d/1xHnLKPCaXrpEe1ccRh_7-IqgNbAlzQsZVc-wr1W4ng8/edit#))
* [promotion creative requirements]() - `Design DRI to link to new tab on relevant use case creative googledoc` - [handbook for more info]()
* [promotion creative final]() - `Design DRI to link to repo in GitLab`

### :books:  Issues to Create
<details>
<summary>REGARDLESS IF PURCHASED Expand below for quick links to issues to be created and linked to the epic.</summary>

* [ ] Develop: [/analysts/ commentary page and /analysts/ page]() - AR `need new issue template`
* [ ] Activate: [Organic Social Issue](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/issues/new?issuable_template=social-general-request) - Social
* [ ] Activate: [Blog Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/issues/new#?issuable_template=blog-post-pitch) - Editorial
* [ ] Activate: [PR Announcement Issue](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/issues/new?issuable_template=announcement) - PR
* [ ] Activate Internally: [Sales Enablement Issue]() - `or confirm it's on agenda for cadenced updates to sales` - AR
</details>

<details>
<summary>IF PURCHASED Expand below for quick links to issues to be created and linked to the epic.</summary>

* [ ] Manage: [Asset Expiration Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=Gated-Content-Expiration-Analysts-MPM) - `need to break these tasks out` MPM to organize for now
* [ ] Prep: [Digital Design Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/-/issues/new?issuable_template=NEEDTHISSSSS) - Design `need issue template`
* [ ] Prep: [Landing Page Copy Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=marketo-landing-page-copy) - AR
* [ ] Develop: [Marketo Landing Page & Automation Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-creation) - MPM
* [ ] Develop: [Pathfactory Track Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=pathfactory_request) - MPM
* [ ] Activate: [Resource Page Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=resource-page-addition) - MPM
* [ ] Activate: [Digital Marketing Promotion Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=mktg-promotion-template) - DMP
* [ ] Activate: [Homepage Feature (only when applicable)](https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/new?issuable_template=request-website-homepage-promotion) - Growth
</details>

cc @jgragnola 

/label ~"Content Marketing" ~"Gated Content" ~"Analyst Relations" ~"Marketing Programs" ~"mktg-status::plan"

Competitive Content (delivered by competitive)

When Competitive Intelligence determines that they will be purchasing a comparison PDF to be gated, they are responsible for creating the epics and associated issues to request work of all relevant teams (outlined below to try to make it efficient, comprehensive, and repeatable!).

View the workback timeline calculator here

Organizing competitive content epics and issues

🏷️ Label statuses:

  1. Competitive Asset Epic: Competitive DRI creates epic (using code below)
  2. Related Issues: Competitive DRI creates the issues as designated in the epic code, and associates to the competitive asset epic

Please note that if details and landing page copy are not provided, the MPM is blocked and will not be able to gate the resource.

> NAME EPIC: *[type] Exact Name of Content* (ex. [comparison pdf] Bitbucket vs. GitLab)

> START DATE = date epic opened, DUE DATE = launch date

<!-- DELETE THIS LINE AND ABOVE ONCE EPIC EDITED -->

## Launch date: 

## Live Pages: [overall comparison page]() and [comparison pdf download page]() - `to be added when live`

#### :key: Key Details
* **Competitive Intelligence:** 
* **Product Marketing:** 
* **Marketing Programs:** 
* **Content Marketing:** 
* **Official Content Name:** 
* **Official Content Type:** 
* **Validity / Expiration Date (if relevant):** (start date - end date)
* [ ] [main salesforce program]()
* [ ] [main marketo campaign]()

## :memo: Documents to Reference
* [content draft]() - `link to temporary unlicensed version when available`
* [promotion creative requirements]() - `Design DRI to link to new tab on relevant use case creative googledoc`
* [promotion creative final]() - `Design DRI to link to repo in GitLab`

### :books:  Issues to Create
<details>
<summary>Expand below for quick links to issues to be created and linked to the epic.</summary>

* [ ] Develop: [Overall Comparison Page Issue]() - competitive `need new issue template`
* [ ] Activate: [Organic Social Issue](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/issues/new?issuable_template=social-general-request) - Social
* [ ] Activate: [Blog Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/issues/new#?issuable_template=blog-post-pitch) - Editorial
* [ ] Activate: [PR Announcement Issue](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/issues/new?issuable_template=announcement) - PR
* [ ] Activate Internally: [Sales Enablement Issue]() - `or confirm it's on agenda for cadenced updates to sales` - competitive
* [ ] Prep: [Digital Design Issue](https://gitlab.com/gitlab-com/marketing/growth-marketing/-/issues/new?issuable_template=NEEDTHISSSSS) - Design `need issue template`
* [ ] Prep: [Landing Page Copy Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=marketo-landing-page-copy) - competitive
* [ ] Develop: [Marketo Landing Page & Automation Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=marketo-landing-page-creation) - MPM
* [ ] Develop: [Pathfactory Track Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=pathfactory_request) - MPM
* [ ] Activate: [Resource Page Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=resource-page-addition) - MPM
* [ ] Activate: [Digital Marketing Promotion Issue](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/issues/new?issuable_template=mktg-promotion-template) - DMP
* [ ] Activate: [Homepage Feature (only when applicable)](https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/new?issuable_template=request-website-homepage-promotion) - Growth
</details>

cc @jgragnola 

/label ~"Content Marketing" ~"Gated Content" ~competition ~"Marketing Programs" ~"mktg-status::plan"

Where to upload final asset

To be completed by the Marketing Program Manager.

Add to Pathfactory

Add to /downloads/ repository (only available and recommended for assets under 2 MB size) The purpose of this step is to make it possible to flip the autoresponder if Pathfactory were to have an outtage, at which point, we would still have the PDF version available in Marketo for a quick turnaround.

  1. Save the pdf to your computer with naming convention [asset-type]-short-name-asset, ex: ebook-agile-delivery-models
  2. Navigate to the (de-indexed) resource/download directory
  3. Where it says www-gitlab-com / source / resources / +, click the plus drop down and select "Upload File"
  4. Upload the file you've saved to your computer with the naming convention above
  5. For commit message, add Upload [Asset Type]: [Asset Name], check box for "create new merge request", name your merge request, and click "Upload file"
  6. Add description to MR, complete the author checklist, assign to @jgragnola and click "Submit Merge Request"
  7. In your Marketo program, for the pdfVersion My Token, add the naming convention above which will be available when the MR is merged. (the token should look like http://about.gitlab.com/resources/downloads/add-file-name-here.pdf)

Marketo automation and landing page creation

Watch the video tutorial > - to be created

:exclamation: Dependencies: delivery of final asset, completion of final landing page copy, and final asset added to pathfactory and placed in a track must be complete before setting up the Marketo program.

The TL;DR of what you'll do:

Create Marketo program, tokens, and SFDC campaign sync

Edit registration page and thank you page URLs

Activate smart campaign(s)

Update SFDC campaign

Test live registration page and flows

Add new content to the Resources page

  1. Begin a new MR from the resources yml
  2. Use the code below to add a new entry with the relevant variables
  3. Add commit message Add [resource name] to Resources page, rename your target branch, leave "start a new merge request with these changes" and click "Commit Changes"
  4. Assign the merge request to yourself
  5. When you've tested the MR in the review app and all looks correct (remember to test the filtering!), assign to @jgragnola
  6. Comment to @jgragnola that the MR is ready to merge

Code:

- title: 'Add name of resource - shorten if necessary'
  url: 
  image: /images/resources/security.png
  type: 'eBook'
  topics:
    - 
    - 
  solutions:
    - 
    - 
  teaser: 'Add a teaser that relates to the contents of the resource'

Example:

- title: '10 Steps Every CISO Should Take to Secure Next-Gen Software'
  url: /resources/ebook-ciso-secure-software/
  image: /images/resources/security.png
  type: 'eBook'
  topics:
    - DevSecOps
    - Security
  solutions:
    - Security and quality
  teaser: 'Learn the three shifts of next-gen software and how they impact security.'

IMAGES to choose from (select one): *Shortcuts to Images Folder

TOPICS to choose from (add all that apply):

How to retire analyst assets when they expire

How to gate a piece of content on a standard gated content landing page

PHASING OUT EVERYTHING BELOW THIS LINE.

The below is being phased out and being replaced with a tokenized program and Marketo landing pages built within the template for efficiency gains.

If you are going to be uploading your gated asset as a PDF instead of PathFactory link, follow the below steps first by creating a MR for the PDF before MR for landing page. If you create the landing page MR before your PDF MR, you will get a 404 error when clicking the download link after the form fill.

  1. Upload your PDF to the resource/download directory
    • Ex: ebook-agile-delivery-models
  2. Leave commit message including the asset type and asset name you are uploading
    • In your MR, scroll down to the Changes tab and on your asset click the button view on about@gitlab.com and use that as your URL anywhere that you would be using a PathFactory link in the remaining steps (landing page code, Marketo token)
  3. Follow the remaining steps for the Gated Content process

1️⃣ Start with the Landing Page on about.gitlab

  1. Navigate to the /resources/ repo
  2. Click the + dropdown and select New Directory
  3. Add the directory name using the following syntax: [type]-short-name
    • Name is very important as this is the url for the landing page!
    • Keep it short, and use hyphens between words. (i.e. ebook-ciso-secure-software)
  4. Add commit message to name your Merge request using syntax Add [content type] landing page - [name of content] (i.e. Add ebook landing page - CISO Secure Software)
  5. Create a name for the target branch - NEVER leave it as the master (i.e. jax-ebook-ciso)
  6. On the next screen (New Merge Request), add WIP: to the beginning of the title and add a quick description (Add LP for [content name] will suffice)
  7. Assign to Jackie Gragnola and scroll down, check the box for “Delete source branch when merge request is accepted”
  8. Click Submit Merge Request
  9. You’ve now created the merge request, but you need to add the file (code) for the landing page itself within the directory
  10. Click on the link to the right of “Request to Merge” and you will enter the branch you’ve created with your MR
  11. Click the Source folder, then Resources and click into the new directory as you named it
  12. Click the + dropdown and select New File
  13. Where it says “File Name” at the top, type in index.html.haml
  14. Copy the following code: (see below)
---
layout: default
title: `add title here, don’t use colons`
suppress_header: true
extra_css:
  - styles-2018.css
destination_url: "`add the pathfactory url when available&lb_email="
form_id: "1002"
form_type: "resources"
cta_title: "Download the `type: eBook, etc`"
cta_date: 
cta_subtitle: 
link_text: "Click here to download the `type: eBook, etc`."
success_message: "You will also receive a copy of the `type: eBook, etc`sent to your inbox shortly."
---

.wrapper
  .page-illustrated-header-container
    = partial "includes/icons/gitlab-icon-pattern-header.svg"
    .container
      .header-container-content
        %h1.page-headline `add headline from copy doc`
        %h2.page-headline `add subhead from copy doc`

  .content-container
    .wrapper.container{ role: "main" }
      .row
        .col-xs-12.col-md-6.col-md-offset-1
          .content-section
            %p `Add P1 from copy doc`
            
            %p `Add P2 from copy doc`

            %h3 What you’ll learn in this `type: eBook, etc.`:
            %ul
              %li `add bullet 1`
              %li `add bullet 2`
              %li `add bullet 3`

            %p `add closing paragraph`

        .col-md-4.col-md-offset-1
          = partial "includes/form-to-resource", locals: { destination_url: current_page.data.destination_url, form_id: current_page.data.form_id, form_type: current_page.data.form_type, cta_title: current_page.data.cta_title, cta_date: current_page.data.cta_date, cta_subtitle: current_page.data.cta_subtitle, link_text: current_page.data.link_text, success_message: current_page.data.success_message }
  1. Back in your MR, paste, the code where the file begins with 1.
  2. Update the variables in the codeIn all the places in snippet code
    • Be sure to remove the back-tick code symbols so that the copy does not turn red on the landing page. This is just to be used as a guideline while editing the landing page.
  3. If you don’t yet have a pathfactory link, leave the copy in that place. When you have the Pathfactory link in a later step, you’ll edit the MR with the new link before pushing live (see later step)
  4. Important! If there is a colon : in your title, replace with a dash - for the page title, as it will break the page.
  5. In the Commit Message below your code, add a note that you’re adding the code for the landing page
  6. Click Commit Changes
  7. Now, while you wait for the pipeline to approve, move onto the next step in Marketo to facilitate the flows and tracking of the program.

2️⃣ Create Marketo Program

  1. Clone the gated content template in Marketo
  2. Choose clone to A campaign folder
  3. Use naming syntax [yyyy]_[type]_NameOfAsset (i.e. 2019_eBook_CISOSecureSoftware) - keep this short
  4. Add to folder: Gated Content > Content Marketing
  5. Leave description blank and select “create”
  6. When the new program loads, copy the url of the Marketo program and add to the description of the gating issue under DRIs and Links

3️⃣ Create Salesforce Program

  1. Create SFDC program (Program Summary > Salesforce campaign sync > click "not set" and choose "Create New" from dropdown) - leave the name as auto-populates, and add the epic url to the description and "Save"
  2. Click save, and navigate to the campaigns view in Salesforce
  3. Choose the “Gated Content” campaign view and make sure it is in order by Created Date (first column) from latest to earliest creation. Your campaign should appear at the top.
  4. Click into your campaign and change the owner to your name
  5. Copy the url of the Salesforce campaign and add to the description of the gating issue under DRIs and Links

4️⃣ Update the Marketo Tokens

  1. Navigate to the My Tokens section of the Marketo program, and make the following edits:
    • Content Download URL: add the PathFactory link after the asset is loaded into Pathfactory and added to a track. This is provided by the Pathfactory DRI. You may need to update the confirmation email button link to follow PathFactory link criteria or to remove extra tokens that will break the PDF token.
    • Content Epic URL: the url to the overall epic of the content
    • Content Title: the content title as it appears on the asset - not necessarily what is displayed as the landing page header on the copy doc (i.e. 10 Steps Every CISO Should Take to Secure Next-Gen Software)
    • Content Type: select the appropriate content type (i.e. leave just eBook)
    • UTM: leave the code that is originally there, and at the end of the code, add the name of the Marketo program, removing any underscores or special characters (i.e. 2019eBookCISOSecureSoftware)
    • Copy and paste the 3 bullets from the content copy document into the 3 tokens aligned to the bullets

5️⃣ Preview the emails

  1. Preview the confirmation email to make sure that the tokens appear correctly.
  2. If you haven’t uploaded to Pathfactory and received a final link, your button will be broken. When you add that to the Marketo tokens, the button will work properly.

6️⃣ Edit, Review, and Activate Marketo Smart Campaign

  1. In the 01 Downloaded Content smart campaign, under Smart Listadd the url created in step 1 to the /resources/ link in the referrer constraint (i.e. add ebook-ciso-secure-software after/resources/ so that it is /resources/ebook-ciso-secure-software
    • In the Flow section, review the steps. It should include:
    • Send Email: Confirmation email from your program (this automatically pulls in)
    • Remove from flow with “choice” that if email address contains @gitlab.com it should not continue the steps
    • Change program status in your program to Gated Content > Downloaded
    • Interesting moment using tokens with “Web” type, and description: Downloaded the {{my.content type}}: “{{my.Content Title}}
    • Send alert to Noneand {{my.mpm owner email address}} (reps receive MQL alerts, so this only triggers to the MPM and can be filtered out of your email if desired).
    • Change data value if Acquisition Program is empty to now be the current program
    • Change data value if Person Source is empty to be “Gated Content - {{my.content type}}”
    • Change data value if Initial Source is empty to be “Gated Content - {{my.content type}}”
  2. In the Schedule section, check that it’s set for each person to run through the flow every 7 days and click Activate

7️⃣ Test Your Page in the Review App

  1. Navigate back to your MR in GitLab
  2. When your pipeline has complete, click “View App” and add the URL you chose for your page (i.e. add /resources/ebook-ciso-secure-softwareto the end of the view app url
  3. Fill out the form using your test lead (using email syntax [your email]+[name]@gitlab.com - i.e. jgragnola+george@gitlab)
  4. Check in the Marketo program that it triggered the autoresponder, addition to the program, and alert.
  5. In your inbox, check the confirmation copy and urls.
  6. If this fires properly, return to the MR and assign to Jackie with a comment to ping her and let her know it’s ready to merge.
  7. Check off all completed actions on the issue.
  8. When the MR merges into the master, it will appear at the URL you determined.
  9. When it has appeared, test it once more with a different test lead email address, and confirm that everything fires as desired.

8️⃣ Add Your Page to the Rsesources Page

  1. Begin a new MR from the resources yml
  2. Use the code below to add a new entry with the relevant variables
  3. Add a commit message, rename your target branch, leave "start a new merge request with these changes" and click "Commit Changes"
  4. Update the name of your merge request to be Add [resource name] to Resource Center
  5. Assign the merge request to yourself
  6. When you've tested the MR in the review app and all looks correct (remember to test the filtering!), assign to Jackie
  7. Comment to Jackie that the MR is ready to merge

🏁 Notify the Team

  1. Comment in the issue with the final URL and a message that the page is now live and working as intended.
  2. Close out the issue.
GIT is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license