Blog Open Source GitPitch Slideshow Presentations for Developers on GitLab
Published on October 3, 2016
6 min read

GitPitch Slideshow Presentations for Developers on GitLab

Learn how can help you present your ideas and code to any audience.


Today I would like to introduce GitPitch, a slideshow presentation service for developers on GitLab. GitPitch supports building, sharing, and presenting online and offline slideshow presentations. Presentations powered entirely by Markdown and Git.

As developers and advocates, we often need to communicate with diverse audiences about our code. We find ourselves needing to present everything from designs and best practices, to code snippets and complete frameworks. Our audiences include colleagues, clients, customers, end-users, and sometimes meetups and conferences.

With GitPitch, we no longer need to turn to external toolsets like Keynote or Powerpoint to prepare for these kinds of presentations. In fact, now the only tools we need are the tools we live in, our preferred code editor and a GitLab repo. And with these tools we can quickly create compelling, responsive, online and offline slideshow presentations.


How GitPitch Works

As GitLab users, we are already familiar with the convention of adding a to our projects. GitPitch introduces a new convention for GitLab users, called

As soon as we add a markdown file to the root directory of our project, GitPitch instantly creates an online slideshow presentation based on the content in that file. That slideshow presentation is then automatically made available at its public URL:

Here user and project matches our user and project names respectively and branch matches the repository branch where we committed our file. Note, the /branch can be omitted from the slideshow URL if we are referencing the master branch.

GitPitch In 60 Seconds

To experience just how simple it is to create a GitPitch slideshow presentation follow along with this short tutorial.

Step 1: Create

Using the GitLab web editor, or your preferred code editor, create a file called in the root directory of your repo, then add and save the following Markdown content:

# Flux

An application architecture for React


### Flux Design

- Dispatcher: Manages Data Flow
- Stores: Handle State & Logic
- Views: Render Data via React


![Flux Explained](

Before moving on to the next step it's worthwhile to note the following:

  1. The file name is case sensitive.
  2. The file content is standard Markdown.
  3. The #HSLIDE markdown fragment acts as a delimiter between slides.

Using #HSLIDE is another GitPitch convention, acting as a delimiter to denote the separation between content on different slides in your presentation. You can use custom delimiters if you prefer. For this example, when GitPitch processes the Markdown content it will result in a simple presentation with just three slides.

Step 2: Commit

If you used the GitLab web editor in step 1 then go directly to step 3. Otherwise, manually add this file to the root directory of your Git repo and push to GitLab:

git add
git commit -m "Added my first GitPitch slideshow content."
git push

Step 3: Done!

Your GitPitch slideshow presentation is now waiting for you to share or present at its public URL. To see a live demonstration of this slideshow presentation click here. Your own presentation should look a lot like this:


Immediately you can download your slideshow for offline presentation, print it as a PDF document, or share it on social media. But first, you might want to apply some personal touches using GitPitch customization, the topic we'll look at next.

Note that beyond support for standard Markdown on presentation slides, GitPitch delivers a number of features tailored for developers, including support for code blocks, GitHub GIST, math formulas along with image, and video support. The full set of GitPitch features are documented on the GitPitch Wiki. To see a live slideshow demonstration of these features try out the GitPitch Kitchen Sink.

GitPitch Customization

As with any presentation, a GitPitch presentation not only needs to capture and render compelling content, it also needs to be able to reflect the style, image or brand of the associated project, product or organization. To help us develop a strong visual identity for our slideshow presentations, GitPitch offers six distinct visual themes out-of-the-box. See the GitPitch Themes Wiki page to learn more.


Building on these base themes we can further customize the look and feel of our slideshow presentations using background images, our own logo, and even custom CSS to bend the pixels to our needs.


GitPitch and GitLab Workflow

The markdown for our slideshow presentation becomes just another file in our GitLab project repo. Therefore all of the benefits we currently enjoy when working with GitLab Workflow apply equally when developing our slideshow presentations.

Given GitPitch can render a slideshow presentation for any branch within a public GitLab repo, using feature branches also offers an excellent way to customize a presentation's content for different target audiences. For example:

  1. Branch to tailor code snippets for a Scala rather than Java audience.
  2. Branch to adjust the presentation focus for a dev-ops audience.
  3. Branch to emphasize participation of a partner or customer for a specific conference.

Some common, in-person workflows are also greatly improved when working with GitPitch presentations. For example, how often have you heard this simple request following a successful presentation:

Can you please send me your slides?

If our presentation lives outside of our GitLab project it is very easy to misplace or forget to follow up. With GitPitch, a simple answer is always at hand:

The slideshow presentation is part of the project on GitLab, just click on the GitPitch Badge found in the project

Going Faster from Idea to Presentation

GitLab champions new, modern development tools and practices that foster collaboration and information sharing to help developers go faster from idea to production. GitPitch embraces and extends this approach by helping individuals, teams and organizations to promote, pitch and present their ideas and code to ever wider audiences.

Note, by default the GitPitch service on integrates with If you are interested in using GitPitch with your own GitLab server see this note on the GitPitch Wiki.

Like GitLab, GitPitch itself is an open source project, built on some wonderful open source software. See the GitPitch website for details. And remember, getting started couldn't be easier. GitPitch requires no sign-up. And no configuration. Just add ;)

About Guest Author

David Russell is a freelance developer, consultant for-hire, open source contributor and the creator of GitPitch. You can reach David on Twitter @gitpitch.

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedback

Ready to get started?

See what your team could do with a unified DevSecOps Platform.

Get free trial

New to GitLab and not sure where to start?

Get started guide

Learn about what GitLab can do for your team

Talk to an expert