diff options
| author | Avinesh Tripathi <73980067+AvineshTripathi@users.noreply.github.com> | 2022-10-08 01:05:49 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-08 01:05:49 +0530 |
| commit | 38c1e81aa4d5404ab3389ef54c77642ca84c1166 (patch) | |
| tree | 028b4e887028511a3d339b42734b539520764485 | |
| parent | 95ddb6c1694f22a43b53a458b8469cf08c3b59fe (diff) | |
Update and rename Events.md to Comms-Events.md
| -rw-r--r-- | communication/marketing-team/role-handbooks/Comms-Events.md (renamed from communication/marketing-team/role-handbooks/Events.md) | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/communication/marketing-team/role-handbooks/Events.md b/communication/marketing-team/role-handbooks/Comms-Events.md index b7560501..f11f3c23 100644 --- a/communication/marketing-team/role-handbooks/Events.md +++ b/communication/marketing-team/role-handbooks/Comms-Events.md @@ -1,4 +1,4 @@ -# Event Co-ordinator Role Handbook +# Comms Events Lead Role Handbook ## Overview @@ -24,7 +24,7 @@ Time Commitment: ## Expectations and tasjs -The core task for the role would be to stay current on [upcoming]() events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). +The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). - Creating a communication schedule - what, when, how, who - Promoting on different platforms like |