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.

Teams

Content Marketing

The Content Marketing team is comprised of content marketers who specialize in different subject areas: Development, Operations, Security, and Customers. This team is responsible for content strategy and new content creation for our content pillars and integrated campaigns. They focus on developing consistent content journey experiences and primarily create resource-driven content such as case studies, eBooks, explainer videos, infographics, reports, whitepapers, and web articles. The goal of the Content Marketing team is to attract interest and position GitLab as a trusted resource through informational and educational content.

Contact the Content Marketing team if you need assistance with:

  1. Content planning or creation for a campaign
  2. Copywriting for a campaign
  3. Editing and/or review of long-form content (eBook, whitepaper, report)
  4. Landing page copywriting for a gated asset
  5. New gated content or web article content idea
  6. Nurture email copywriting

Visit the Content Marketing Handbook page to learn more about the Content Marketing team and instructions on how to request help.

Digital Production

The Digital Production team is comprised of video/audio editors and producers who manage GitLab's digital content presence. This team is responsible for video marketing strategy (including GitLab's branded YouTube channel), podcasting, and digital media production. They primarily focus on storytelling by creating entertaining video and audio content in order to build an emotional connection with audiences. The goal of the Digital Production team is to build trust and an emotional connection between GitLab and our audiences.

Contact the Digital Marketing team if you need assistance with:

  1. Approval to post a video on GitLab's branded YouTube channel
  2. Branding elements (video bumpers, lower thirds, etc.) for a video
  3. New video or podcast idea
  4. Review a video for brand compliance
  5. Video editing
  6. Video production

Visit the Digital Production Handbook page to learn more about the Digital Production team and instructions on how to request help.

Editorial

The Editorial team is comprised of content editors who manage the GitLab blog.

Editorial calendar

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

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

Legend

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

Communication

Please use the following Slack channels:

Issue trackers

Labels

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

GitLab.com 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.

Definitions

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.

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 marketing operations.

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