mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 08:58:41 +00:00
Drew bakerfdm event preparation (#14247)
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
This commit is contained in:
parent
c7e6b282ec
commit
b9a8872fab
2 changed files with 27 additions and 0 deletions
|
|
@ -51,6 +51,8 @@ Here are some topics for social media posts:
|
|||
### Ads
|
||||
Fleet uses advertising to spread awareness through a broader audience and foster greater engagement within user communities. The more people actively using Fleet, or contributing, the better Fleet will be.
|
||||
|
||||
### Events
|
||||
It's important for Fleet to engage at events. This provides an opportunity to directly engage with potential users and contributors, build relationships, gather feedback, and create a stronger sense of community and trust.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
|
|
@ -116,6 +118,17 @@ Any changes to the current running ads visible to a user, including designs, key
|
|||
2. Compare existing ads against the newly proposed ad within the corresponding ad platform. ([Google Ads](https://ads.google.com/home/), [LinkedIn Campaign Manager](https://www.linkedin.com/campaignmanager/), etc.)
|
||||
3. If your change is approved, Field Marketer makes changes and creates a calendar reminder to check performance two weeks from the date changes were made.
|
||||
|
||||
### Book an event
|
||||
For an event to be considered, booked, and scheduled, we follow the event issue template.
|
||||
|
||||
1. Create a [new GitHub issue for the #g-marketing board](https://fleetdm.com/handbook/marketing#contact-us) and select the "Event-preparation" template..
|
||||
2. Drag the issue into the "🗓 Ideas for future events" column.
|
||||
|
||||
Once approval has been received, move the event into the "🗓 Planned events" column.
|
||||
|
||||
### Review ongoing events
|
||||
Check the "🗓 Planned events" column in [#g-marketing board](https://app.zenhub.com/workspaces/g-marketing-64e6c8e2d35c7f001a457b7f/board) and continue to work through steps in each event's issue.
|
||||
|
||||
## Rituals
|
||||
<rituals :rituals="rituals['handbook/marketing/marketing.rituals.yml']"></rituals>
|
||||
|
||||
|
|
|
|||
|
|
@ -21,3 +21,17 @@
|
|||
description: "Complete draft orders." # example of a longer thing: description: "[Prioritizing next sprint](https://fleetdm.com/handbook/company/communication)"
|
||||
moreInfoUrl: "https://fleetdm.com/handbook/marketing#process-pending-swag-requests-from-the-website" #URL used to highlight "description:" test in table
|
||||
dri: "drewbakerfdm" # DRI for ritual (assignee if autoIssue) (TODO display GitHub proflie pic instead of name or title)
|
||||
-
|
||||
task: "Review ongoing events"
|
||||
startedOn: "2023-10-02"
|
||||
frequency: "Daily"
|
||||
description: "Check 🗓️ Planned events and complete steps in each issue"
|
||||
moreInfoUrl: "https://fleetdm.com/handbook/marketing#review-ongoing-events"
|
||||
dri: "drewbakerfdm"
|
||||
-
|
||||
task: "Book an event"
|
||||
startedOn: "2023-10-02"
|
||||
frequency: "Weekly"
|
||||
description: "Populate 🗓️ Ideas for future events"
|
||||
moreInfoUrl: "https://fleetdm.com/handbook/marketing#book-an-event"
|
||||
dri: "drewbakerfdm"
|
||||
|
|
|
|||
Loading…
Reference in a new issue