<iclass="fas fa-bullhorn fa-fw color-orange font-awesome"></i> Welcome to the GitLab Marketing Handbook
{.h2}
The GitLab Marketing team operates as one team and is organized by the following departments: [Integrated Marketing](/handbook/marketing/#integrated-marketing), [Brand and Product Marketing](/handbook/marketing/#brand-and-product-marketing), [Marketing Operations and Analytics](/handbook/marketing/#marketing-operations-and-analytics), [Sales Development](/handbook/marketing/#sales-development), [Growth](/handbook/marketing/growth/), [Corporate Communications](/handbook/marketing/#corporate-communications), and [Developer Relations](/handbook/marketing/#developer-relations). This page documents our shared team philosophy and processes, while the individual department handbooks contain more detailed information.
The GitLab Marketing team operates as one team and is organized by the following departments: [Integrated Marketing](/handbook/marketing/#integrated-marketing), [Brand and Product Marketing](/handbook/marketing/#brand-and-product-marketing), [Marketing Operations and Analytics](/handbook/marketing/#marketing-operations-and-analytics), [Sales Development](/handbook/marketing/#sales-development), [Enterprise Data](/handbook/marketing/#enterprise-data), [Corporate Communications](/handbook/marketing/#corporate-communications), and [Developer Relations](/handbook/marketing/#developer-relations). This page documents our shared team philosophy and processes, while the individual department handbooks contain more detailed information.
## Marketing Purpose
@@ -95,12 +95,12 @@ Weekly Direct Reports Meetings (Each manager with their direct reports)
| Topic | Where to reach out | Sub-Team |
| ------ | ------ | ------ |
| Blog posts, webcasts, the newsletter or other marketing content | `#content` | [Content] |
| External PR (public relations) agency, discuss GitLab media mentions, and evaluate speaking/podcasting/commentary opportunities | `#external-comms` | [Corporate Communications] |
| Anything regarding the marketing website and website development | `#digital-experience-team` | [Digital experience] |
| Questions about tools in the [marketing tech stack](marketing-operations/), evaluating new marketing tools, marketing system process improvement | `#mktgops` | Marketing Operations |
| Blog posts, webcasts, the newsletter or other marketing content | `#content` | [Content](/handbook/marketing/brand-and-product-marketing/content/) |
| External PR (public relations) agency, discuss GitLab media mentions, and evaluate speaking/podcasting/commentary opportunities | `#external-comms` | [Corporate Communications](/handbook/marketing/corporate-communications/) |
| Anything regarding the marketing website and website development | `#digital-experience-team` | [Digital experience](/handbook/marketing/digital-experience/) |
| Questions about tools in the [marketing tech stack](/handbook/marketing/marketing-operations/), evaluating new marketing tools, marketing system process improvement | `#mktgops` | Marketing Operations |
A complete list of marketing slack channels can be found [here](/handbook/marketing/#marketing-slack-channels).
@@ -112,32 +112,32 @@ A complete list of marketing slack channels can be found [here](/handbook/market
### CMO Requests
Please follow the [CMO handbook] for review request workflows, and communication guidelines.
Please follow the [CMO handbook](/handbook/marketing/cmo/) for review request workflows, and communication guidelines.
### Social Requests
All teams are responsible for requesting social posts themselves. If you are not the DRI on a specific category or campaign and want to request a social post, please reach out to the teams' point person identified below as a first step. Team Members in these roles reserve the right to say no to your request. If they say yes, coordinate with them to [create a new social request issue](integrated-marketing/digital-strategy/social-marketing/) so that the social team can process the request and schedule the post(s). The point person on the team or a member of the marketing or social teams may adjust copy to ensure consistency in brand voice.
All teams are responsible for requesting social posts themselves. If you are not the DRI on a specific category or campaign and want to request a social post, please reach out to the teams' point person identified below as a first step. Team Members in these roles reserve the right to say no to your request. If they say yes, coordinate with them to [create a new social request issue](/handbook/marketing/integrated-marketing/digital-strategy/social-marketing/) so that the social team can process the request and schedule the post(s). The point person on the team or a member of the marketing or social teams may adjust copy to ensure consistency in brand voice.
- User questions/comments on Twitter/X: [Social Marketing](/handbook/marketing/integrated-marketing/digital-strategy/social-marketing/) or [Developer Relations](/handbook/marketing/developer-relations/) team
- Leadgen campaigns: [Content](/handbook/marketing/brand-and-product-marketing/content/) team
- UX Design: UX Lead
- Press/media coverage: Post in `#external-comms` for assistance
- Social media, RTs of mentions, CEO Statements/posts: Post in `#social_media_action` for assistance
- Press/media coverage: Post in `#external-comms` for assistance from the [Corporate Communications](/handbook/marketing/corporate-communications/) team
- Social media, reshares of mentions, CEO Statements/posts: Post in `#social_media_action` for assistance
### Company Spokesperson
Speaking on behalf of GitLab at a conference, to media or on a podcast as a GitLab team member is a significant responsibility. Please see the [Corporate Communications Handbook Page](corporate-communications/) for guidelines and trainings.
Speaking on behalf of GitLab at a conference, to media or on a podcast as a GitLab team member is a significant responsibility. Please see the [Corporate Communications Handbook Page](/handbook/marketing/corporate-communications/) for guidelines and trainings.
- Technical community posts/tutorials: [Developer Advocate] and Blog editorial team
- CEO statements/updates: [CMO](cmo/)
- All other blog posts: [Blog editorial team](brand-and-product-marketing/content/)
- Technical community posts/tutorials: [Developer Advocacy](/handbook/marketing/developer-relations/developer-advocacy/) and [Blog editorial](/handbook/marketing/brand-and-product-marketing/content/) team
- CEO statements/updates: [CMO](/handbook/marketing/cmo/)
- All other blog posts: [Blog editorial team](/handbook/marketing/brand-and-product-marketing/content/)
Guidelines for how to pitch and submit a blog, including templates and formatting, can be found in the [Blog Handbook](blog/).
Guidelines for how to pitch and submit a blog, including templates and formatting, can be found in the [Blog Handbook](/handbook/marketing/blog/).
### Newsletter
@@ -155,13 +155,13 @@ Newsletter requests should be submitted no less than 5 business days before the
**Community Newsletter**
The community newsletter is managed by the [Developer Relations] team, dedicated to sharing relevant developer content, highlighting contribution opportunities, and updating community members on upcoming events. We aim to keep our contributors involved and connected with the wider community. This newsletter will not be used to drive or generate leads.
The community newsletter is managed by the [Developer Relations](/handbook/marketing/developer-relations/) team, dedicated to sharing relevant developer content, highlighting contribution opportunities, and updating community members on upcoming events. We aim to keep our contributors involved and connected with the wider community. This newsletter will not be used to drive or generate leads.
To submit to the newsletter, please follow the [handbook instructions](/handbook/marketing/developer-relations/developer-advocacy/community-newsletter/#submissions).
### Sponsorship
We are happy to sponsor events and meet-ups where a marketing benefit exists, subject to approval by [Field Marketing] Managers. These sponsorships may be in cash or in kind, depending on individual circumstances.
We are happy to sponsor events and meet-ups where a marketing benefit exists, subject to approval by [Field Marketing](/handbook/marketing/field-marketing/) Managers. These sponsorships may be in cash or in kind, depending on individual circumstances.
Organizational or project sponsorships may also be considered where a marketing benefit exists. Typically, these sponsorships will be in kind - e.g., developer time commitments, or [subsidized / free GitLab licenses](https://about.gitlab.com/blog/2018/06/05/gitlab-ultimate-and-gold-free-for-education-and-open-source/).
@@ -180,10 +180,10 @@ We use Slack internally as a communication tool. The Marketing channels are as f
-`#cfp`: All event call for papers will be posted here. Learn more in the [speaking resources](/handbook/marketing/corporate-communications/speaking-resources/) handbook.
-`#cmo`: [CMO review requests](/job-families/chief-marketing-officer/) and content shares.
-`#content`: Questions about blog posts, webcasts, the newsletter or other [marketing content](brand-and-product-marketing/content/)? This is the place to ask.
-`#content`: Questions about blog posts, webcasts, the newsletter or other [marketing content](/handbook/marketing/brand-and-product-marketing/content/)? This is the place to ask.
-`#developer-relations`: A channel for the [developer relations](/handbook/marketing/developer-relations/) team to collaborate.
-`#dev-advocacy-team`: Discuss the latest tech in DevSecOps and Cloud-Native with the [Developer Advocate](/handbook/marketing/developer-relations/developer-advocacy/) tea. You can request speakers and ask for technical content collaboration and guidance.
-`#digital-experience-team`: Channel for connecting with the [website development and design teams](digital-experience/)
-`#dev-advocacy-team`: Discuss the latest tech in DevSecOps and Cloud-Native with the [Developer Advocacy](/handbook/marketing/developer-relations/developer-advocacy/) team. You can request speakers, customer consultancy and technical content collaboration and guidance.
-`#digital-experience-team`: Channel for connecting with the [website development and design teams](/handbook/marketing/digital-experience/)
-`#digital-marketing`: Channel for all advertising, website analytic and general digital programs.
-`#external-comms`: To collaborate with our external PR (public relations) agency, discuss GitLab media mentions, and evaluate speaking/podcasting/commentary opportunities.
-`#fieldmarketing`: Discuss, ask questions, stay up-to-date on events that are being organized by Field Marketing
@@ -250,35 +250,35 @@ Product and Brand Marketing represents the GitLab story at the brand, solution,
Handbook Links
{.h4}
- [Brand]
- [Merchandise Handling (Swag)]
-[Product and Solution Marketing](brand-and-product-marketing/product-and-solution-marketing/)
The Integrated Marketing team is focused on creating awareness, generating demand and collaborating with the broader ecosystem globally, through a co-ordinated and unified approach. We connect the dots and bring content and messaging to life by leveraging various channels as our levers to communicate across segments, regions and personas.
The team includes [Field Marketing], [Channel](/handbook/marketing/channel-marketing/), [Corporate Events], [Account Based Marketing], [Campaigns], [Lifecycle Marketing], [Digital Strategy] and [Digital Experience].
The team includes [Field Marketing](/handbook/marketing/field-marketing/), [Global Channel Marketing](/handbook/marketing/channel-marketing/), [Corporate Events](/handbook/marketing/integrated-marketing/corporate-events/), [Account Based Marketing](/handbook/marketing/account-based-marketing/), [Integrated Campaigns](/handbook/marketing/campaigns/), [Lifecycle Marketing](/handbook/marketing/lifecycle-marketing/), [Digital Strategy](/handbook/marketing/integrated-marketing/digital-strategy/) and [Digital Experience](/handbook/marketing/digital-experience/).
The GitLab Growth department is dedicated to making it easier for teams to find value and increased efficiency within the GitLab platform. We work across stages within the product experience to make the product as easy as possible to adopt and use.
The GitLab Enterprise Data Team is responsible for empowering every GitLab team member to contribute to the data program and generate business value from our data assets.
