Content library and workflows for Developer Advocates

The Developer Advocacy team creates content that can be used for campaigns, field enablement, product launch support, use case adoption, customer demos, and general learning and onboarding. All contents and activities the team participates in are tracked in issues following team workflows.

On this page

• Request content
• Content library
• Content creation guidelines
• Content distribution

Request content

If you need an updated or newly created content asset, please create an issue using the content request template.

Existing content work items are grouped in the FY Content strategy epic.

Content library

The following sections provide an overview of all content assets and links to find them. You can search for relevant content on this page and contact the team in the linked content epics or in the #developer-advocacy Slack channel.

For demos, choose the format that fits your audience and environment:

• Product tours: Short, guided walkthroughs that introduce a feature and its value.
• Click-through demos: Product simulations for rehearsing or presenting a workflow without a live environment, including offline use.
• Projects: Demo environments for hands-on exploration, workshops, and live demonstrations. Review each environment’s setup instructions before use.

Highspot

The team’s content is distributed in the content platforms below, and in Highspot in topic and type-specific spots, for example, GitLab Duo (AI) and Customer Outreach.

Blog posts

Browse selected posts by theme. Author names link to their full list of blog posts. Posts covering more than one theme are listed once under their main topic.

AI

DevSecOps

Community

Product tours

Product tours are self-guided journeys emphasizing the ‘What’ of a feature to directly showcase value aspects.

Explore the Demo Zone → - Maintained by the Developer Advocacy team and hosted on the GitLab marketing website, our centralized demo hub brings together all product tours in one location, organized across three key areas: Duo Agent Platform, Security, and DevSecOps Platform.

Videos

GitLab YouTube channel

• GitLab Demos
• GitLab Duo Demos
• GitLab Snapshots
• GitLab Snapshots - español
• GitLab Snapshots - português

GitLab Unfiltered YouTube channel

• Developer Advocacy - Talk recordings, workshops, and community engagements
• Dev Advocacy: GitLab Duo Agent Platform use cases
• Contributor Success AI Catalog / Duo Agent Platform Demos - User stories demonstrating the power of the AI catalog

Vimeo folder

• Developer Relations (internal)

Maintained talks

These talk slide decks provide storytelling for talks at events, speaking engagements, customer workshops, etc. You can use the slide decks for your own talks, workshops, etc. or repurpose specific slides into new stories. Reach out to the DRI in #developer-advocacy for questions and feedback.

These talks are maintained:

Workshops

The Developer Advocacy team maintains workshops in different product and focus areas. A workshop can be of different types: Hands-on with audience participating live in the exercises (training course), or showcase live demo/programming sessions where the audience engages with questions. Workshops should be created in collaboration with the Solution Architect and Customer Success teams, and aligned with business goals.

Note: Specific customer focussed workshops can be requested following the customer consultancy handbook.

Maintained documentation

Developer advocates authored and maintain the following documentation pages, with practical and technical examples aiding adoption and efficiency use cases.

Click-through Demos

Click-through demos are product simulation demonstrations that can be used for self-guided training. They are invaluable for delivering demos to customers in areas with limited internet connectivity or complex environments, where preparation is necessary to showcase the flow. Toggle off the click boxes and speaker notes using fn+F2 to experience the real look and feel of the product.

Product Adoption Initiatives

• Support Orbit / Knowledge Graph launch (demos, use cases, research) - FY27
• Support GitLab DAP launch: Status, feature tracker, enablement - DevRel FY27

Projects

Source code, demo projects, workshops, tutorials, research, etc. are documented in the Projects handbook. This includes use cases for GitLab Duo (AI), CI/CD components, DevSecOps and Security, Workspaces, GitLab API, etc.

Content creation guidelines

Video production guidelines

Equipment recommendations

Microphone

• Recommended: Logitech Blue Yeti
• Use the same microphone setup for all recordings to ensure consistent audio quality across videos
• Test your microphone levels before recording to ensure smooth, clear audio
• Position the microphone consistently (6-12 inches from your mouth) to maintain audio quality

Camera

• Recommended: Logitech MX Brio Ultra HD 4k
• Position at eye level for the most natural appearance

Lighting

• Recommended: Elgato Key Light
• Use consistent lighting for all on-camera recordings

Background

• Keep backgrounds clean and professional
• Avoid clutter, distracting items, or busy patterns
• Use a neutral background or a simple, organized workspace
• Ensure the background is well-lit and free of harsh shadows
• Consistency across videos creates a more professional appearance

Software

Screen recording

• Recommended tools: Quicktime, OBS, or Screen Studio

Post-editing

• Adobe Premiere Pro (video cuts, audio gain boost, etc.)

On-camera presentation tips

When recording videos with yourself on camera:

• Speak naturally and conversationally - avoid reading from scripts
• Use bullet points or talking points instead of full scripts to maintain authenticity
• Make eye contact with the camera to connect with viewers
• Be yourself - authenticity builds trust and connection with the audience
• If you make a mistake, pause and restart that section naturally rather than trying to power through
• Practice your key points beforehand, but deliver them conversationally during recording

Video settings

Aspect ratio and resolution

• Set recording window size to 16:9 aspect ratio
• Common resolution: 1920×1080 (16:9) or 2880×1750 for screen recordings
• If connected to a 4K monitor, it may be easier to capture from your laptop

Screen Studio settings for Brand team videos

• Remove all Zooms (Brand team will add as needed)
• Do not record webcam/user view
• Set rounded corners and padding to 0% to maximize screen size
• Turn on Always use pointer cursor
• Set cursor size to 1.2x, use the left-most Cursor style option
• Export: Format - MP4, Resolution - 1080p, Compression - Web

Screen Studio settings for other content (social, YouTube, webinars)

• Discuss zoom usage with content stakeholders and review to ensure correct focus
• Webcam use is encouraged - seeing real people builds trust and connection
  • To hide webcam post-recording: click Camera icon and toggle Hide camera slider
• Borders/frames can be helpful but ensure they don’t impact content readability
• Turn on Always use pointer cursor
• Set cursor size to 1.2x, use the left-most Cursor style option
• Export: Format - MP4, Resolution - 1080p, Compression - Web

Demo environment setup

User accounts

• Prefer the demo-tanuki account for brand demos (login is in 1Password, Marketing vault)
• Use your own accounts (or GDK admin) for all other demos

GitLab UI in Chrome browser

• Zoom: 125% (or 110% as alternative)
• Minimized bookmarks bar (cmd shift b)
• Theme: White
• GitLab layout width: Fluid (Profile > Settings > Layout width)

IDEs - See Dev Environments for full details

• Be overly generous with zoom so viewers can clearly see what’s happening on screen
• VS Code: Zoom (cmd + +) once or twice more than you think you need to
• JetBrains: Settings > Appearance & Behavior > Appearance > Accessibility > Zoom - 125% worked best in tests
• Simplify your IDE by closing unnecessary tabs and toolbar items
• Disable all AI integrations from IDE vendors
• Simplify view by hiding unnecessary icons or using Zen mode (cmd+k+z)

Additional guidance: dev environments (internal handbook)

Checklist for external content requests

When fulfilling external video content requests, confirm:

1. Video should include audio voice-over or text-only voice-over script
2. Output artifact format (default: mp4)
3. Delivery format (default: 16:9, 1920x1080) or custom format needed
4. Where the video will be used (YouTube, blog embed, social media)
5. SRT file with subtitles for captioning

Recording with Screen Studio

Screen Studio captures screen areas and windows, combines them with webcam views, and uses intelligent automated “zooming into scenes” with a simple editing UI.

Note: Usage of the “Shareable Links” feature is not approved, as it uploads recordings to Screen Studio’s cloud storage.

To start a recording, use the minimal overlay UI:

Steps:

1. Select Display, Window, or Area

   • Screen Studio can record any resolution, but 16:9 or 4:3 is recommended (see specifications)
   • For Area: Select the aspect ratio and drag through the recording region

   

2. Click record to start recording

After finishing, save the project first, then open the editor.

In the editor:

1. Review all settings, video alignments, Zoom timeline, etc.
2. Ensure you’re following the specifications in the Video settings section
3. Save the project
4. Click Export → Export to file
5. In the export dialog, choose mp4 format

Project management:

• Screen Studio saves projects in ~/Screen Studio Projects folder
• Project files use .screenstudio extension and contain raw video files and settings
• You can inspect them with ls on the terminal
• Re-open them from the Screen Studio project list:

After delivery: Upload all video files (exported artifacts and Screen Studio Projects) to the team Google Drive to save local storage.

Screen Studio recording specifications

Follow the settings detailed in the Video settings section above.

Screen Studio clips for social media

Short product video clips for social media effectively showcase features and capabilities. Follow these guidelines:

Settings:

1. Video length: ~30 seconds
2. No audio recording
3. Recording window: 1280 x 960
4. Output aspect ratio: 4:3
5. Rounded corners: 20
6. Padding: 4%
7. Cursor size: 3x
8. Always pointer cursor
9. Background color: #7759c2

Chrome setup: Avoid recording the Chrome toolbar (no address bar or tabs) to keep focus on GitLab. Launch Chrome in app mode at 1280 x 960:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --app=https://gitlab.com/gitlab-da/projects/cheap-flights --window-size=1280,960

Replace the --app= URL with your target page/project.

Recording with OBS

OBS allows greater control and flexibility for screen recordings, with the trade-off of a more complicated setup and editing process.

Key concepts:

Scene - A collection of sources recorded simultaneously

Sources - Audio, screen recordings, webcams, etc.

• Click the + icon to add sources
• Common sources:
  • macOS Screen Capture: screen recordings
  • Audio Input Capture: direct voice recording
  • Video Capture Input: speaker/webcam in the recording
• For Macbook screen recording: use macOS Screen Capture, name it, and right-click to edit properties
• Properties: Choose between screens (laptop vs monitor) and capture type (whole screen, window, or application)

Recommended preferences:

OBS > Preferences > Video:

• Base (Canvas) Resolution: 1920x1080, Aspect ratio 16:9
• Output (Scaled) Resolution: 1920x1080, Aspect ratio 16:9

OBS > Preferences > Output > Dropdown: Advanced

• Enable “Recording > Automatically remux to mp4” (required for Adobe Premiere Pro, which cannot import mkv containers)

Additional resources:

• OBS Recording Studio Guide
• Developer Advocacy showcase notes (internal) and recording (public)

Post-editing with Adobe Premiere Pro

Access: Requires an Access Request (example)

Resources: Review the Developer Advocacy showcase notes (internal) and recording (public)

Audio gain boost for professional broadcaster microphones

If using a professional broadcaster microphone (e.g., Shure SM7B) and the audio gain is too low, try these options:

Hardware solution (recommended)

• Audio interface + Cloudlifter greatly improves results
• The SM7B microphone needs extra gain before reaching your computer

OBS Recording

1. Increase audio gain in OBS during recordings
2. Locate Source > Audio Capture Device
3. Right-click and select Filters
4. Set Gain to +10 or +20dB
5. Configure filters:
   • Noise Suppression: RNNoise or Speex
   • Compressor: Ratio 3:1, Threshold -18dB, Attack 6ms, Release 60ms
   • Limiter: Threshold -6dB, Release 60ms

Tip: Ask Claude for best practice settings (prompt: How to boost audio in OBS for a Shure SM7B microphone as input?)

Post-editing Screen Studio recordings

1. Edit the exported recording in Adobe Premiere Pro
2. Create a new project and add the video source in the media browser
3. Drag and drop the video into the editor
4. Right-click on the audio track and select Audio Gain
5. Choose Set Gain to: and enter 25 dB

Additional recording equipment resources

• FY26Q2 discussion and tips (internal)
• @dnsmichi’s audio setup

Uploading videos to GitLab Unfiltered channel

Starting from July 2025, team members are encouraged to upload videos to GitLab Unfiltered using GitLab Video Scanner, which is an internal service to help team members mitigate token leak risks in videos published to the GitLab Unfiltered Channel.

Product tours guidelines

Guidelines for creating GitLab tours with Navattic

1. Keep it concise - Product tours should have 5 to 12 steps, each delivering clear value. Unlike tutorials, product tours should be quick and engaging.
2. Provide context - Add links to blog posts and documentation in pop-up dialogs for additional resources.
3. Apply GitLab branding - In theme settings, select “GitLab Branding [Navattic Team]” for consistent design.
4. Use the appropriate capture type:
   • Web captures (preferred) create an in-product experience
   • Screenshots for non-web-based applications (e.g., IDEs)
5. Set the correct resolution - When capturing in Chrome, use 1440x900 (Navattic’s recommended resolution). Use the built-in resize tool in the Navattic recording toolbar.
6. Include a call to action - The final step should feature a CTA, typically a Free Trial link.
7. Use Beacons to highlight relevant elements - Apply the Highlight appearance setting to emphasize key elements.
8. Enable keyboard navigation - Allow users to navigate the tour using arrow keys for a smoother experience.
9. Use Presenter Mode - Hide pop-ups when necessary for cleaner visual presentation.
10. Set pop-ups appropriately:
    • Modals with heavy backdrop for first and last steps
    • Tooltips for intermediate steps, enabling Backdrop setting when appropriate
11. Use action-specific labels - Use labels like “Commit,” “Install,” or “Submit” instead of “Next” to make users feel actively engaged.
12. Review examples - Review existing product tours to understand the preferred format.
13. Request review - Before releasing any public-facing product tour, request a review from the Developer Advocacy team.

Requesting access to Navattic

If your team has special requirements for tours and you want to develop tours with Navattic:

• 3-month trial license available to team members with valid business justification
• Active users may receive extended access or additional licenses as needed
• Inactive users’ licenses may be reassigned to other team members
• To request access: Open a request in Lumos (available in the Okta dashboard)

Questions? Contact us in #developer-advocacy

Adding a new Navattic user (Developer Advocacy team process)

When a team member requests Navattic access, follow this process:

1. Receive request - Navattic admin receives Lumos request via Slack or email
2. Validate - Ensure requester provides valid business justification
3. Check availability - Review Navattic users tracking spreadsheet for license availability
4. Approve in Lumos - Once validated, approve the access request for Okta access
5. Send Navattic invite - Invite team member with Builder role under GitLab team
6. Share guidelines - Send Navattic guidelines
7. Communicate trial period - Inform team member of default 3-month access period
8. Update tracking - Add to Navattic users tracking spreadsheet with name, email, start date, and expected end date
9. Add to Slack - Invite to #navattic-updates channel

Publishing product tours

Product tours are published in these locations:

• Developer Advocacy content library
• Highspot
• GitLab documentation (follow the style guide for demo links)
• Demo Hub portal - Centralized platform for all product demos

Select tours may also be featured on the website.

Contributing to product tours

The Developer Advocacy team creates product tours showcasing key workflows and new features like Advanced SAST, GitLab Duo, GitLab Duo with Amazon Q, and more. You can contribute by proposing additional tours with content, script, and environment.

How to collaborate:

1. Use the product tour submission template to propose your idea
2. Answer all template questions for effective evaluation
3. Developer Advocacy team will review and either:
   • Greenlight the tour and suggest timeline based on priorities
   • Offer suggestions for improvements
   • Explain why it might not fit and offer alternatives
4. Once approved, use the product tour template (Google Doc) to draft the script (link in submission template)
5. Add script link in a comment on the submission issue
6. Developer Advocacy team will collaborate on the script, create the tour in Navattic, and publish to official targets (website, docs, Highspot, handbook)

Content distribution

UTMs for URL tagging and tracking

The Developer Advocacy team follows the Marketing UTM strategy. The utm_content prefix for the Developer Advocacy team is de_, allowing easy data filtering in Sisense.

Use the UTM builder to create UTM codes for your campaigns.

Content distribution workflow

After content is published, follow these distribution steps:

General setup:

1. Use the UTM builder to create UTM codes and short URLs

Documentation and community:

1. Add helpful tutorial blog posts and demos to GitLab documentation
   • Follow contribution docs and create related topics headings if needed
   • Create MR with content short URLs and request review from assigned technical writer
   • Example: Add tutorial blog posts to workspaces docs
2. Share on community platforms:
   • GitLab Forum
   • r/gitlab subreddit
   • For broader topics: other subreddits or blogging sites like dev.to

Social media:

1. Draft social media copy
   • See Content Sharing for platform tips
   • Review message tips for engagement ideas
2. Suggest content on EveryoneSocial for team member sharing
   • How to suggest content on EveryoneSocial
3. After posting, share in #social-media-action Slack channel to request social team promotion

GitLab teams:

1. Post field-useful content to Highspot
2. Share update in #developer-advocacy Slack channel using this template:

:results-tanuki: <Content type> published: <title>

Social short UTM URLs:

1. LinkedIn:
2. Twitter:
3. Mastodon:

Content epic: <URL>

Thanks/cc @teammembers

Example:

:results-tanuki:  Blog published: Set up your infrastructure for on-demand, cloud-based development environments in GitLab

Social short UTM URLs:

1. LinkedIn:
2. Twitter:
3. Mastodon:

Content epic: <URL>

Thanks a lot @HelpfulCoworker for editing this long read :handshake: :purple_heart:

View page source - Edit this page - please contribute.