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

Content Marketing

On this page

The Content team includes audience development, editorial, social marketing, video production, and content strategy, development, and operations. The Content Marketing team is responsible for the stewardship of GitLab's audiences, users, customers, and partners' content needs. Content marketing creates engaging, inspiring, and relevant content, executing integrated content programs to deliver useful and cohesive content experiences that build trust and preference for GitLab.

Roles on the Content Marketing team include:

Mission & vision

Our content marketing 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

Chat

Please use the following Slack channels:

Issue trackers

Requesting content and copy reviews

  1. If you are looking for content to include in an email, send to a customer, or share on social, check the GitLab blog first.
  2. If you need help finding relevant content to use, ask for help in the #content channel.
  3. 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
  4. 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.

Defintions

Content stage defintions

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.

Tracking content

Topic Use Example
AWS Content that relates Amazon Web Services. Likely use cases are case studies where the customer uses GitLab + AWS and integration information & tutorials. How to set up multi-account AWS SAM deployments with GitLab CI/CD
Agile delivery Content that relates to the agile delivery process decision framework which emphasizes incremental and iterative planning. What is an Agile mindset?
Agile software development Content that relates to the agile software development methodology which emphasizes cross-functional collaboration, continual improvement, and early delivery How to use GitLab for Agile software development
Application modernization    
Automation    
Azure    
CI/CD    
Cloud computing    
Cloud native    
Containers    
DevOps    
DevSecOps    
Digital transformation    
GKE    
Git    
Jenkins    
Kubernetes    
Microservices    
Multicloud    
Open source    
SCM    
Security    
Single application    
Software development    
Toolchain    
VSM    
Workflow    

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

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 section above.

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. 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 compontents. 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 Consieration Solution page Content & product marketing
2 Consideration Webcast Product & technical marketing
1 Purchase Demo Technical marketing
1 Purchase Data sheet Product marketing

Sources:

Current pillars

Application modernization
header header header
1. Organizations want to deploy faster and generate revenue through innovation but don’t have the architecture to support those goals. 2. Legacy systems slow down development with complicated processes, open networks to security risks, and are difficult to maintain - leaving little room in IT budgets for innovating. 3. Leveraging microservices and committing to a modernization strategy puts organizations on the path to development efficiency.
4. Adopting Continuous Integration helps developers work faster and build better applications through automated testing. Errors are caught automatically so developers can focus on other tasks. 5. Continuous Delivery/Deployment takes Continuous Integration a step further. New code is pushed more frequently through an automated release process, and developers can watch their work go live in minutes. 6. Streamlining the toolchain and adopting cloud native architecture improves IT spend and increases efficiency by automating processes. Teams can use GitLab as the primary mechanism to configure, build, test, deploy, and manage their microservices.
Reduce cycle time

Improve software cycle time to deliver business value faster.

1. Every company is becoming a software company, increasing the demand for better software, faster. Reducing the time between thinking of an idea and having the code in production is vital to providing value to customers. 2. If an organization is too slow to innovate, its competitors can rapidly absorb the market by becoming the first organization to meet the needs of customers. 3. Agile planning and DevOps delivery have demonstrated reliable and scalable solutions to streamline and accelerate application delivery.
4. Teams use a variety of tools to automate integration, test code, manage digital assets, scan for vulnerabilities, and deploy/configure applications, but each tool adds a layer of complexity in a team’s workflow, so teams are forced to waste cycle time tinkering on tools and not delivering business value. 5. To reduce cycle time, teams should look for ways to consolidate interrelated development activities. Development teams need a simple, comprehensive toolchain that can easily build, test, and deliver applications without the waste and overhead of managing dozens of disparate tools and integrations. 6. Simplifying the toolchain empowers teams to focus on innovation and delivering value to customers faster. Organizations can use GitLab to address the challenges of rapidly building and delivering business applications to remain competitive.

Topics: Agile delivery, value stream management

Secure apps

Application security for developers.

1. Applications have seen exponential growth in the frequency of attacks (and successful breaches) in recent years. The rise of cloud computing, containers, and the use of third party code, in addition to the need to ship quickly and frequently, have thrust security to the forefront of software development.Security can no longer be treated as an afterthought. 2. Regulations like GDPR and massive attacks like WannaCry and NotPetya have made security a business ultimatum. This takes the code written to protect your business to the front line of commercial cyber defense. Secure apps, APIs, and data storage could mean the difference between a 20 year future or a three year future for your company. 3. VPs of AppDev need to work with both their direct teams and broader organizations to establish a culture of security: Everyone should feel responsible for and empowered to make your product or service as secure as possible. Security needs to be top of mind for every project and iteration.
4. To help developers achieve and abide by this mindset, it’s important that they are given the education and resources necessary to understand how and why it’s critical for them to consider security from the moment they write their first line of code. 5. Shifting left is the answer: Building security in at the end is an inefficient and cost-inducing process. If developers start with security at the beginning of the SDLC, teams will find it easier to keep security tightly coupled with updates and iterations as they work within an agile or DevOps process/methodology. 6. Usability must be top of mind when building security in from the start. Enabling developers with a tool like GitLab - which integrates vulnerability testing into the development process, keeping developers in the same tool and reducing workflow disruption - will be crucial in getting developer buy-in.

Topics: application security, devsecops

Messaging for Verticals

When to develop vertical messaging: The key is to determine if an industry has a certain pain point that another industry does not share. You need to describe the problem (using industry specific terminology, if necessary) and also how your product solves these problems for them. Additionally, you can create high-level messaging and then branch off; for example if multiple industries are very security conscious, create security focused marketing, and adapt to select high value verticals.