Draft: Blog: Top 5 Security Concerns for Developers (2025-20-10)

Closes https://gitlab.com/gitlab-com/marketing/brand-product-marketing/content-strategy-and-ops/blog/-/issues/451

Checklist for writer

• Link to issue added, and set to closed when this merge request is merged
• Due date added to the merge request title for the desired publish date
• Review app checked for any formatting issues (check code boxes, mermaid charts, etc.)
• Any required internal or external approval for this blog post has been granted (please leave a comment with details in the issue)
• Reviews by Legal team if necessary according to SAFE guidelines
• Assign to @Sgittlen for review and publication

File structure checklist for manual file creation

• When creating a branch name start of the branch name needs to be cms/blogPost/ so that it will appear in Decap Workflow tab while the merge request is open.
• Blog post should be a .yml file under the /blog/ folder for the appropiate locale, for an English blog post this would be /content/en-us/blog/
• the yml file has the correct structure:

seo: # Blog team will fill this area in
  title: the blog post title (55-60 characters)
  description: the blog post description (no more than 155 characters)
config: # Blog team will fill this in
  slug: this should be the same as the filename without the extension. e.g. if your file is my-awesome-blog.yml, this value should be 'my-awesome-blog'
  featured: false
  template: BlogPost
content:
  title: the blog post title # Ideal length - 55-60 characters
  description: the blog post description # Ideal length - no more than 155 characters
  authors:
    - Blog post author # Format: Sandra Gittlen (if this is your first time contributing, leave blank)
  heroImage: blog/hero%20images/workflow_1800x945.png # Blog team will fill this in
  date: '2021-03-31'
  category: engineering # Blog team will fill this in
  tags: # Blog team will fill this in
    - community
  body: |
    the blog post body text in markdown

After the blog has been published:

• Share on your social media channels
  • Add ?utm_medium=social&utm_campaign=blog&utm_content=advocacy to the end of the blog URL when you share on social media, for data tracking. Your link should look like this:https://about.gitlab.com/blog/blog-title/?utm_medium=social&utm_campaign=blog&utm_content=advocacy
• After you've shared on your social media profiles, select one of the posts and link it in the #social_media_action Slack channel for everyone to engage with your post. The GitLab social team may engage or even share your social media post to amplify the work.
• To learn more about how to use your own social media channels for GitLab, check out our team member social media guidelines here.