Skip to content

Dev Advocacy: Add Bluesky social media tips (starter packs, etc.), refine messaging/media tips, handbook cleanup

Michael Friedrich requested to merge da-social-media-bluesky into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

Bluesky is a new social media platform, and the tech community started migrating from Twitter/X in late October 2024. Developer Advocates are encouraged to explore new content distribution platforms, and best practices and learnings need to be documented. gitlab-com/marketing/developer-relations/developer-advocacy/developer-advocacy-meta#277

This MR is the first iteration to enable Dev Advocates, team members and wider community members to quickly start with Bluesky

  1. Add Bluesky tips section including
    1. Account and settings, plus domain setup and getting started guides
    2. Team members and brand social account table.
    3. Bluesky Starter Packs - team member maintained, and community resources for DevRel, DevOps, CloudNative, Ruby, etc.
    4. Follower and engagement tips
  2. Refactor general messaging and media tips
    1. Add message limits, add media size and conversion tips (heic-2-jpg tools/tips handbook)
  3. De-prioritize Twitter/X as a platform, and focus on LinkedIn, with experimental Bluesky
  4. Remove outdated content for thought leadership and content sources (not the primary target of this MR, future cleanup will follow)

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Dev Advocacy: Add Bluesky social media tips, refine messaging/media requirements, remove outdated X tips
Edited by Michael Friedrich

Merge request reports