Changes for content/handbook/ceo/shadow.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -421,7 +421,7 @@ A tweet storm is a series of X/Twitter posts usually made as replies in a single
1. Consider looking at the CEO's social media accounts for tone and style.
1. Each tweet can contain 280 characters, URLs are counted differently. Make sure to test each tweet with the Twitter web form to tweet.
1. When you add URLs, use the [card validator](https://cards-dev.twitter.com/validator) to render a preview. This can help to refine the tweet text.
1. More message tips can be found in the [Developer Advocacy on Social Media handbook](/handbook/marketing/developer-relations/developer-advocacy/social-media/#message-tips).
1. More message tips can be found in the [Developer Advocacy on Social Media handbook](/handbook/marketing/product-and-technical-marketing/developer-advocacy/social-media/#message-tips).
1.[2021-12-15 example for Chief of Staff videos](https://docs.google.com/document/d/1BL2ZBtqF5fKdQox0p2lde_qv-75rXwYmQNHvKJnUR-8/edit) (internal).
1. Once complete, change the document's Owner to the [Chief of Staff to the CEO](/job-description-library/chief-executive-officer/chief-of-staff/).
Changes for content/handbook/communication/_index.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -313,7 +313,7 @@ Below are a few things to remember when creating issues:
1. Once a feature is [**done**](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#definition-of-done), update the description to add a link to the corresponding documentation. When using a Search Engine, issues often appear before documentation pages, which makes it harder to find the relevant information about the feature.
1. Write issues so that they exclude private information. This way, the issue can be public. Only use confidential issues, if the issue must contain [non-public information](/handbook/communication/confidentiality-levels/#not-public). **Note:** Confidential issues are [accessible to all members of the project with Reporter access and above](https://docs.gitlab.com/ee/user/project/issues/confidential_issues.html#permissions-and-access-to-confidential-issues). You may consider using a Google Doc for items that require a stricter level of confidentiality.
1. If the content within a public issue transitions to become what is deemed confidential [non-public information](/handbook/communication/confidentiality-levels/#not-public), the issue may be made confidential.
1. If the content of a public issue draws comments that are deemed in violation of our [code of conduct](https://about.gitlab.com/community/contribute/code-of-conduct/) the issue may be locked and may [undergo moderation](/handbook/marketing/developer-relations/workflows-tools/code-of-conduct-enforcement/#overview).
1. If the content of a public issue draws comments that are deemed in violation of our [code of conduct](https://about.gitlab.com/community/contribute/code-of-conduct/) the issue may be locked and may [undergo moderation](/handbook/marketing/product-and-technical-marketing/developer-advocacy/tools-and-platforms/code-of-conduct-enforcement/#overview).
Changes for content/handbook/engineering/devops/create/engineers/conferences.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -56,7 +56,7 @@ On top of all benefits of attending the conference mentioned above, when speakin
* Bolster your personal brand and spread the word about GitLab
* Improve your public speaking and communication skills
For more information on speaking at conferences, check out the [Developer Advocacy CFPs](/handbook/marketing/developer-relations/developer-advocacy/cfps/) handbook.
For more information on speaking at conferences, check out the [Developer Advocacy CFPs](/handbook/marketing/product-and-technical-marketing/developer-advocacy/cfps/) handbook.
## How do I go about requesting permission to attend a conference?
Changes for content/handbook/engineering/open-source/growth-strategy.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -124,7 +124,7 @@ Provide an outstanding, highly efficient and fast contributor experience, from o
#### Product & engineering alignment
***Why:** Within [product groups](/handbook/company/structure/#product-groups), contribution submissions, backlog, and technology stack vary. Healthy community backlog alignment and the establishment of a common best practice for outreach are vital for contributor success. In addition, there should be a unified & known workflow for Wider Community Contributions.
