Talk/Whitepaper/Playbook - Remote development/engineering best practices
Developer Relations Content Request
Suggested title format: "Content type: Title - Author - Publish Month, Publish Year"
Dates should use ISO dates, see https://about.gitlab.com/handbook/communication/#writing-style-guidelines -->
Activity Summary
Please provide a brief overview of the request.
Request details
Please answer the following questions to help understand your request and its priority.
- What is the business goal?
- A: Educate our users and customers about remote collaboration and engineering best practices.
- Who is the target persona/audience? What is the size of the audience?
- A: DevOps teams, engineering teams, team leaders, C-level
- What is the best content type (blog post, video, how-to) to deliver this message?
- A: Talk storytelling, recording, narrative
- How will this content be distributed?
- A: Slide deck, recording
- How does this content help our audience?
- A: Learn about best practices in a remote work environment (engineering, debugging, hackathons, collaboration in issues, reviews, automation, etc.)
- How does this content help us achieve our goals?
- A: Awareness for GitLab, and how an AI-powered DevSecOps platform enables remote engineering efficiency
Team or Individual DRIs
Note: to be assigned by the Developer Relations team. DevRel team members: Please add appropriate team label upon assignment.
Relevant Issues, Epics or resources
/cc @gitlab-de @akramer