To be removed and linked to Brand & Digital best practices page when created
We create landing pages in several locations. Marketo is the most efficient option, using tokens and automation pre-built into programs for more speedy and consistent exection. The events yml creates landing pages when specific code is included. Gated content pages are created using code and then added as listings in the /resources/ yml. Campaign pages are currently created on about.gitlab.com.
Note: this requires a Marketo license with access to make and approve landing pages.
The following section point to more detailed processes for Marketo landing pages based on landing page type, plus general information for knowledge sharing on creation process.
To build the most advanced and efficient landing page processes in Marketo, we utilize
My Tokensin our Marketo program templates along with character limits based on conversion best practices to write copy.
Curious how to estimate when a landing page due date should be set? We've tried to make it easy with a workback, so that you can also clearly see the dependencies for a landing page to be created (including landing page copy, which is a separate issue teamplate).
My Tokens) for the template you are creatingAssets folder, left-click Landing Page > Edit DraftMy Tokens referenced above, with then does not require any edits to the landing page.Preview to ensure all tokens are correctly applied and the page appears as intended (copy, design, etc). Click Preview Actions > Approve and Close.
Landing Page Actions > URL Tools > Edit URL setting. The new URL should reflect our landing page naming conventionconfirmation or sales alert and approve the edits/ at the end of the page URL before the ?. This will likely cause the page to redirect. (Correct example: https://page.gitlab.com/webcast-example?{{my.utm}}). Note that about.gitlab.com pages should use a /.about.gitlab landing page instructions being phased out
Our integrated campaign landing pages are currently created on about.gitlab.
/why/ directory./source/ folder). For example, if it is a localized use case campaign for France, it would use the subfolder /fr/ followed by the French traslation for /why/ (which is /pourquoi/) followed by the url structure.
https://about.gitlab.com/fr-fr/pourquoi/integration-continue-pour-construire-et-tester-plus-rapidement/ whereas the English version is https://about.gitlab.com/why/use-continuous-integration-to-build-and-test-faster/./compare/ directoryWIP: Add landing page for [Campaign Name]+ and select New Fileindex.html.hamlAdd code for new landing page and click Commit changes at the bottom of the pageWIP: at beginning of MR title&lb_email=<email-of-user>) that will ensure Pathfactory recognizes the individual as a known lead, and track the activity back to the lead/contact record.Add to Campaign smart campaign in your Marketo program (note that if you are using your @gitlab.com email address, you will be removed from the flows to avoid inflating program totals for employee form fills)/ at the end of the page URL before the ?. Omitting the / can cause the form not to display on the page. (Correct example: https://about.gitlab.com/webcast-example/?{{my.utm}}). Note that Marketo pages should not use a /.The following landing page code is using the latest landing page design (for the CI and DevSecOps use case integrated campaigns).
---
layout: value-driver
title:
description:
suppress_header: true
extra_css:
- value-driver-6595-control.css
- comparison-page.css
- form-to-resource.css
- just-commit-6595-control.css
destination_url: "&lb_email="
form_id: "1002"
form_type: "resources"
cta_title: ""
cta_date:
cta_subtitle:
link_text: ""
success_message: ""
---
%div#experiment6595.experiment-outer-wrapper
%span.loading-experiment
%div.experiment-container.experiment-control
.wrapper.gitlab-ee-page
.header-hero-banner.header-hero-banner--reduce-cycle{style: 'background-image:url(/images/just-commit/ci-use-case-web-header.png)'}
.container
.row
.col-md-12
%h1.jumbo-heading Main Header
%h3 Subheader
.sub-wrapper.main-content
.container
.row
.col-md-7
.just-commit-intro-text
%p <strong>Short bold intro sentence.</strong> Intro continued.
.col-md-5
.just-commit-form-wrap
= partial "includes/form-to-resource"
.just-commit-highlight-row
.container
.row
.col-md-5
%h3
%ul.checkmark-list
%li
%li
%li
.just-commit-logo-wrap
= partial "includes/home/customer-logos-transparent"
.wrapper-dark
.just-commit-sales-wrap
= partial "includes/contact-sales"
:css
body {
background: #ffffff;
}
.footer {
margin-top: 0;
Example:
---
layout: value-driver
title: Continuous Integration to build and test faster at any scale
description: Simplify and automate to deliver better products faster - together
suppress_header: true
extra_css:
- value-driver-6595-control.css
- comparison-page.css
- form-to-resource.css
- just-commit-6595-control.css
destination_url: "https://learn.gitlab.com/c/the-benefits-of-sing?x=fDT7Bl&lb_email="
form_id: "1002"
form_type: "resources"
cta_title: "Free Instant Download:<br>Benefits of single application CI/CD eBook"
cta_date:
cta_subtitle:
link_text: "Thanks! Click here to view your content."
success_message: "You will also receive a copy of the eBook in your inbox shortly."
---
%div#experiment6595.experiment-outer-wrapper
%span.loading-experiment
%div.experiment-container.experiment-control
.wrapper.gitlab-ee-page
.header-hero-banner.header-hero-banner--reduce-cycle{style: 'background-image:url(/images/just-commit/ci-use-case-web-header.png)'}
.container
.row
.col-md-12
%h1.jumbo-heading Continuous Integration to build and test faster at any scale
%h3 Read this eBook on how to simplify and automate to deliver better products <br> faster - <i> together </i>
.sub-wrapper.main-content
.container
.row
.col-md-7
.just-commit-intro-text
%p <strong>Wrangling multiple tools can be just as frustrating as manual processes.</strong> Complicated toolchains are difficult to maintain and create information silos for teams. In this eBook, learn how Continuous Integration, built into a complete DevOps platform, can increase efficiency, promote collaboration, and provide greater visibility across your entire software development lifecycle.
.col-md-5
.just-commit-form-wrap
= partial "includes/form-to-resource"
.just-commit-highlight-row
.container
.row
.col-md-5
%h3 What you will learn
%ul.checkmark-list
%li How optimized CI automates processes without the added maintenance of plugins
%li How GitLab CI/CD compares to other CI tools
%li The benefits of single application CI vs. traditional CI
.just-commit-logo-wrap
= partial "includes/home/customer-logos-transparent"
.wrapper-dark
.just-commit-sales-wrap
= partial "includes/contact-sales"
:css
body {
background: #ffffff;
}
.footer {
margin-top: 0;
}