Commit 0b5badf5 authored by Jennifer "JJ" Cordz's avatar Jennifer "JJ" Cordz

Merge branch 'fix-typos-marketing-handbook' into 'master'

Fix typos on Marketing Handbook page.

See merge request !17888
parents f5cd38ad 9afb4ad4
Pipeline #42609843 passed with stages
in 12 minutes and 32 seconds
......@@ -76,7 +76,7 @@ Different marketing teams handle different aspects of Integrated Campaigns. Whic
## <i class="fas fa-tasks fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Project Management Guidelines
Marketing uses GitLab for agile project management including [groups](https://docs.gitlab.com/ee/user/group/), [projects](https://docs.gitlab.com/ee/user/project/), [epics](https://docs.gitlab.com/ee/user/group/epics/), [roadmaps](https://docs.gitlab.com/ee/user/group/roadmap/), [issues](https://docs.gitlab.com/ee/user/project/issues/), [lables](https://docs.gitlab.com/ee/user/project/labels.html), and [boards](https://docs.gitlab.com/ee/user/project/issue_board.html). Read through the documentation on each of these GitLab features if you are unfamilar.
Marketing uses GitLab for agile project management including [groups](https://docs.gitlab.com/ee/user/group/), [projects](https://docs.gitlab.com/ee/user/project/), [epics](https://docs.gitlab.com/ee/user/group/epics/), [roadmaps](https://docs.gitlab.com/ee/user/group/roadmap/), [issues](https://docs.gitlab.com/ee/user/project/issues/), [labels](https://docs.gitlab.com/ee/user/project/labels.html), and [boards](https://docs.gitlab.com/ee/user/project/issue_board.html). Read through the documentation on each of these GitLab features if you are unfamilar.
### Groups and projects
......@@ -84,33 +84,33 @@ Marketing uses GitLab for agile project management including [groups](https://do
1. Labels should exist at the group level so they can be used accross projects.
1. The following are the approved marketing projects, CMO approval is needed to begin a new project.
- [Product Marketing](https://gitlab.com/gitlab-com/marketing/product-marketing) (includes PMM, AR, Customer Case studies, etc.)
- [Community Relations[(https://gitlab.com/gitlab-com/marketing/community-relations)]
- [Community Relations](https://gitlab.com/gitlab-com/marketing/community-relations)
- Digital Marketing Programs
- Corporate Marketing (includes content, website, corp events, brand, etc.)
- Marketing Operations
- Field Marketing
- Sales Development/XDR
1. Issues should only be logged in team project (i.e. do no use `marekting/general`)
1. Issues should only be logged in team project (i.e. do no use `marketing/general`)
1. Don't create groups with subgroups (use labels to segment workstreams within a team's project issue tracker.)
### Issues and Epics
1. Each issue represents a discrete unit of work with a deliverable. For example [1](https://gitlab.com/gitlab-com/marketing/product-marketing/issues/10) [2](https://gitlab.com/gitlab-com/marketing/online-growth/issues/8) [3](https://gitlab.com/gitlab-com/marketing/general/issues/2574)
1. Every MR should have an issue so that it can be tracked on issue boards.
1. Epics represent projects that comprise mulitiple issues. (Don't use "meta" issues for this purpose. If you have have existing meta issue you can promote them to epics using the `/promote` slack command.)
1. Epics represent projects that comprise multiple issues. (Don't use "meta" issues for this purpose. If you have have existing meta issue you can promote them to epics using the `/promote` slack command.)
- Epics live at the group level (e.g. issue from multiple marketing projects can be added to an epic.)
- Epics are labeled with a group label of the team that owns the epic.
1. The top 3-5 strategic initatives are tracked in epics using the `CMO` label. (Don't apply the CMO label to other epics.)
1. Roadmaps are used for time-based display of epics with a start and end date. (for example, events and time-based campaings.)
1. Roadmaps are used for time-based display of epics with a start and end date. (for example, events and time-based campaigns.)
### Boards and Labels
1. Each team has one or more boards to track ongoing workstreams.
1. Generally, create a board for each function. (For example PMM has boards for Sales Enablement, Analyst Relations, Customer Relations, etc.)
1. Each boards uses a standard set of columns/labels so that folks can easily understand what is happening on another teams board.
1. Each board uses a standard set of columns/labels so that folks can easily understand what is happening on another teams board.
1. The board labels use group labels with `status:` and one of four statuses. Status labels are used on both issues and MRs:
- **Optional***:`Status:Plan` - work that is proposed, in an exploratory state. To exit the plan stage the work must be assigned to a DRI. The DRI accepts responsiblity for the task by changing the label from `Status:Plan` to `Status:WIP` and creating an MR if appropriate. The plan status is optional, as issues that don't require formal planning can be opened and labeled `Status:WIP`.
- `Status:WIP` - work in progress that has been accepted and assigned to a DRI. Work in this stage should not be merged. Issues and MRs should be prepended with `WIP:`. At GitLab we allow reviewers to start reviewing right away before work is complete. Use [MVCs](https://about.gitlab.com/handbook/values/#iteration): At any time, if the work is complete enough that merging would be better than what current exist the issue should be labeld with `status:review` and `WIP:` should be removed from the title.
- **Optional***: `Status:Review` - work has been completed enough that it is ready for formal review and approval. Work that is approved can be either merged or scheduled. The review status is optional. Work that doesn't require reivew can simply be merged/closed.
- `Status:WIP` - work in progress that has been accepted and assigned to a DRI. Work in this stage should not be merged. Issues and MRs should be prepended with `WIP:`. At GitLab we allow reviewers to start reviewing right away before work is complete. Use [MVCs](https://about.gitlab.com/handbook/values/#iteration): At any time, if the work is complete enough that merging would be better than what current exist the issue should be labeled with `status:review` and `WIP:` should be removed from the title.
- **Optional***: `Status:Review` - work has been completed enough that it is ready for formal review and approval. Work that is approved can be either merged or scheduled. The review status is optional. Work that doesn't require review can simply be merged/closed.
- **Optional**: `Status:Scheduled` - work that is complete but should be scheduled for a future date. The scheduled status is optional as not all work will need to be scheduled.
- `closed` - when work is delivered the issue should be closed.
1. Don't duplicate status labels at the project level. Use group labels (at the Marketing Group level) as much as possible.
......@@ -131,7 +131,7 @@ Sales Development Representatives (SDRs) contact people who work at large organi
### Field Marketing
{: .no_toc}
Field marketers focus on understanding the specific needs of the geographic regions where GitLab operates. They manage marketing activities, such as events and sponsorships, tailored to the needs of the region the activity takes place in.
Field marketers focus on understanding the specific needs of the geographic regions where GitLab operates. They manage marketing activities, such as events and sponsorships, tailored to the needs of the region where the activity takes place.
[Position Description](/job-families/marketing/field-marketing-manager){:.btn .btn-purple-inv}
[Handbook][Field Marketing]{:.btn .btn-purple}
......@@ -161,7 +161,7 @@ Content marketers focus on understanding our audience of developers, IT ops prac
### Digital Marketing Programs
{: .no_toc}
Digital Marketing Programs focuses on executing integrated campaigns, with a digital-first mindset. They are responsible for executing, deploying, tracking emails and supporting both sales and marketing in outbound mass communications.
Digital Marketing Programs focuses on executing integrated campaigns, with a digital-first mindset. They are responsible for executing, deploying, and tracking emails and supporting both sales and marketing in outbound mass communications.
Digital Marketing Programs includes online marketing, focused on managing online advertising, website experiments, and search engine optimization (SEO). Online advertising is aimed at increasing the volume of relevant traffic to GitLab's marketing site, website experiments are focused on improving web traffic-to-form submission conversion, and SEO is aimed at ensuring our marketing site ranks for the search engine keywords our audiences care about.
......@@ -179,7 +179,7 @@ Community Relations includes community advocacy, code contributor program and ev
- How do we make the documentation even better?
- How do we make it even more fun and easy to get started?
- What is engaging developer content for blog, video, social media?
- How do we build our global meetup plan so word of mouth + make it easy to love GitLab?
- How do we build our global meetup plan + make it easy to love GitLab?
- What is the developer GitLab experience?
- How do we use social media to support the community?
- How do field marketing and developer relations work together to support the community?
......@@ -376,8 +376,8 @@ The Marketing team meets bi-weekly to review announcements, strategy development
The meeting should run as follows:
- Prior to the meeting, each functional area lead updates their content in the [Marketing Team Update](https://docs.google.com/document/d/1MWX74j3GLr3drTBF_E9MkQ0sUiIXkzv8T7oZ3mqnoyg/edit) doc.
- The CMO leads off the meeting with announcements, and strategy, company and org updates.
- Each functional lead reviews prior accomplishments and upcoming plans. The lead will also share relevant team updates and share cross-functional asks
- The CMO leads off the meeting with announcements and updates on strategy, company and org.
- Each functional lead reviews prior accomplishments and upcoming plans. The lead will also share relevant team updates and share cross-functional asks.
- The remaining time is used for open discussion and Q&A.
- Interruption is encouraged! Team members are encouraged to interrupt and ask questions throughout.
- All team members are also encouraged to bring forward discussion topics that they want to share with the team or to have covered during the call.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment