Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Global Content Team

What does the Global Content Team do?

The Global Content section includes the content marketing, editorial, and digital production teams. It is responsible for content strategy, development, and operations, including the stewardship of GitLab's audiences, users, customers, and partners' content needs. The Global Content Team creates engaging, inspiring, and relevant content, executing integrated content programs to deliver useful and cohesive content experiences that build trust and preference for GitLab.

Check the FY21 Global Content Epic for more details on our plans and activities for FY21.

Editorial calendar

Adding an event to the editorial calendar

  1. Make sure there is an associated issue for the event. Link the issue in the event description.
  2. Always check "all day event" unless there is a specific time the piece should publish. This is rare and usually only if a blog post is tied to a time-sensitive PR announcement.
  3. Name your event using the following nomenclature: <emoji, title of content, campaign>. Example: 📝 5 Reasons to Use GitLab, Just Commit


Team handbook pages

Job families:

Mission & vision

Our content mission statement mirrors our company mission. We strive to foster an open, transparent, and collaborative world where all digital creators can be active participants regardless of location, skillset, or status. This is the place we share our community's success and learning, helpful information and advice, and inspirational insights.

Our vision is to build the largest and most diverse community of cutting edge co-conspirators who are defining and creating the next generation of software development practices. Our plan to turn our corporate blog in to a digital magazine will allow us to add breadth, depth and support to our participation in and coverage of this space.

Content team responsibilities


Please use the following Slack channels:

Issue trackers


We use the mktg-status:: labels to work status (triage, plan, WIP, design, review, scheduled). group labels

www-gitlab-com project labels

Requesting content team support

Need help finding relevant content to use in an email or to send to a customer? Ask for help in the #content channel.*

##Requesting content and copy reviews

  1. If the content you're looking for doesn't exist and it's a:
    1. Blog post: See the blog handbook
    2. Digital asset (eBook, infographic, report, etc.): open an issue in the corporate marketing project and label it content marketing
    3. Video: open an issue in the corporate marketing project and label it video production
  2. If you need a copyedit, ping @erica. Please give at least 3 days' notice.

Content production

The content team supports many cross-functional marketing initiatives. We aim for content production to be a month ahead of planned events and campaigns so that content is readily available for use. In accordance with our values of iteration and transparency, we publish our proposed content plans at the beginning of each quarter. We don't hoard content for one big launch and instead plan sets of content to execute on each quarter and published each piece of content as it's completed.

Content production is determined and prioritized based on the following:

  1. Corporate GTM themes
  2. Integrated campaigns
  3. Corporate marketing events
  4. Newsworthiness
  5. Brand awareness opportunity

We align our content production to pillars and topics to ensure we're creating a cohesive set of content for our audience to consume. Pillar content is multi-purpose and can be plugged into integrated campaigns, event campaigns, and sales plays.

Content alignment

Content production is aligned to digital campaigns and product messaging.


Content stage / buyer's journey definitions

Awareness (Top)

Users and buyers realize that they have a problem or challenge which could be solved through some sort of outside software or service. At this stage, they are trying to define the scope and the relative impact and size of the problem. They probably do not yet have a solution identified, but are in the process of learning about potential solutions to their specific business problem.

In general, messaging in collateral and content should be focused on educating them about the problems they are facing, the business impact of their problems, and the reality that others are successfully solving the same problem. This is an opportunity for them to learn that GitLab is an authority in addressing their domains.

Consideration (Middle)

Users and buyers understand the problem they are trying to solve and the business impact/value of addressing the problem and are now actively seeking and evaluating potential remedies to their business issue. Typically, they will be considering a range of approaches from better leveraging existing tools to investing in new technologies and vendors. In this stage they are focused on identifying options that meet their specific requirements and needs. While cost will be a consideration, they have not yet made a final decision about how to address their needs. In this stage, they will be defining their budget and overall plans for implementing a solution.

In general, collateral and content designed to reach prospects in this stage of their journey should be focused on positioning GitLab as a viable and compelling solution to their specific problem.

Decision/Purchase (Bottom)

Users and buyers have concluded that they need to invest in solving a specific business problem and are now comparing and evaluating specific options. In this stage, they are evaluating and comparing different options in order to identify the ideal solution for their specific situation. They will consider Fit (technology, process, etc), implementation effort/cost, total cost of ownership and other factors to guide them in making a final selection.

In general, collateral and content designed to reach prospects in this stage of their journey should be focused on key information that a buyer needs to justify GitLab as their chosen solution.

Planning timeline

Pillar strategy is planned annually and reviewed quarterly. Content sets are planned quarterly and reviewed monthly. When planning, we follow the 80/20 rule: 80% of capacity is planned leaving 20% unplanned to react to last minute opportunities.

Content library

Content for us is stored in PathFactory. To request access to PathFactory, submit an access request form.

The content library in PathFactory can be filtered by content type, funnel stage, and topic. Topics are listed and defined in the digital marketing programs management handbook.

Published content should be shared to the #content-updates channel and added to PathFactory with the appropriate tags.

What is a content pillar?

A content pillar is a go to market content strategy that is aligned to a high-level theme (for example, Just Commit) and executed via sets. Often, content pillars are defined based on value drivers and customer use casesin order to support go to market strategy. For example, "Just commit to application modernization" is a content pillar about improving application infrastructure in order to deploy faster. Within this pillar, many topics can be explored (CI/CD, cloud native, DevOps automation, etc.) and the story can be adapted to target different personas or verticals.

We use content pillars to plan our work so we can provide great digital experiences to our audiences. The content team aligns to themes to ensure we are executing strategically and meeting business goals. Pillars allow us to narrow in on a specific topic and audience, and sets help us break our work into more manageable components. Each set created should produce an end-to-end content experience (awareness to decision) for our audience.

Content pillar diagram

What's included in a content set?

Here's an example of what's included in a content set:

Quantity Stage Content Type DRI
4 Awareness Thought leadership blog post Content marketing
1 Awareness Topic webpage Content marketing
1 Awareness Resource Content marketing
4 Consideration Technical blog post Content marketing
1 Consideration Whitepaper Product & technical marketing
1 Consideration Solution page Content & product marketing
2 Consideration Webcast Product & technical marketing
1 Purchase Demo Technical marketing
1 Purchase Data sheet Product marketing