Line Highlights

You can emphasize specific lines of code to direct the audience's attention. Multiple code highlight steps can be added and stepped through for the same code block. An empty highlight step means that no code is highlighted.

Developer Mode

The Slides editor has a developer mode which is useful if you know a bit of HTML and CSS. With this mode active you will be able to modify the underlying HTML of your deck, allowing you to make adjustments that the Slides editor does not provide interface options for.

To enable the developer mode open the editor settings in the bottom left corner:

Editing HTML

The per-slide HTML editor can be accessed from the slide options area. It gives you raw access to the current slide's HTML, allowing you to change anything you like. Note that some elements, such as <script> and <link>, are not allowed for security reasons.

Element Classes (Requires Pro)

As a paying Slides customer you have access to the CSS editor which allows you to add custom styles to your deck. By turning on the developer mode a new "class name" field will appear for any block that you focus. This allows you to easily target a specific element with your CSS.

Here's an example that defines an "upside-down" class using custom CSS and applies it to a text block.

.upside-down {
    transform: scale( 1, -1 );
}

Slide Classes (Requires Pro)

Just like you can add custom classes to individual elements it's also possible to add custom classes at the slide level. This can used to apply broader changes to the whole slide like inverting text and icon colors or changing the slide transition.

Under the hood the slide background element is separate from the slide itself. Here are two examples showing how you'd target the slide contents or slide background using a custom class called "night-sky":

// Targets the slide contents
.slides .night-sky svg path {
    fill: yellow;
}
// Target the slide background
.backgrounds .night-sky {
    background: linear-gradient(0deg, #141528, #0b1bb2);
}

Export HTML

You can access the complete HTML for all slides in your deck inside of the export panel, under "Export to reveal.js". This provides a way of exporting your deck markup and the core Slides styles to reveal.js. There are a few limitations with exporting this way but it should provide a good starting point.

Define API: Create Prefilled Decks (beta)

The define API lets you create a presentation programatically and add it to the current user's Slides account. Presentations you create can include any of the content types that the Slides editor supports. You can even include live data from other sites via iframes.

For example, if you operate a web-based charting service, you can let your users create a presentation containing their fully interactive charts at the click of a button.

If the user isn't already signed in to Slides, they will automatically be prompted to authenticate or sign up. Once signed in, they are able to review the deck and confirm that they want to save it to their account. Here's what that process looks like:

The Request

To start the process you'll need to have the user submit an HTML form towards the https://slides.com/decks/define endpoint. The form needs to contain an input field with the name definition and the value of this input should be the JSON representation of a deck. Once the form is submitted, we'll automatically redirect the user to the appropriate page.

Here's a fully working example:

JSON Examples

Here's the bare minimum JSON you'll need to describe a deck.

{
  "title": "My Deck",
  "slides": [
    { "html": "<h1>Slide 1</h1>" },
    { "html": "<h1>Slide 2</h1>" }
  ]
}

If you want to group multiple slides into one vertical stack you can nest them in an array:

{
  "title": "My Deck",
  "slides": [
    { "markdown": "# Slide 1" },
    [
        { "markdown": "# Vertical Slide 2.1" },
        { "markdown": "# Vertical Slide 2.2" }
    ],
    { "markdown": "# Slide 3" }
  ]
}

The following JSON demonstrates most of the available options.

Note that there are three different ways to define slide content, blocks, HTML and Markdown. The benefit of using content blocks is that the elements you define are separately editable inside of the Slides editor. If you specify content as a string of HTML or Markdown, it will all be grouped into one element and edited as a text box.

{
  "title": "My Deck",
  "description": "Description of My Deck.",
  "width": 1024,
  "height": 576,
  "auto-slide-interval": 0,
  "slide-number": false,
  "loop": false,
  "theme-color": "white",
  "theme-font": "overpass",
  "transition": "slide",
  "slides": [
    {
      "id": "an-optional-slide-id",
      "background-color": "#cccccc",
      "background-image": "https://static.slid.es/images/screenshots/v1/slides-homepage-1440x900.png",
      "background-size": "cover",
      "notes": "My speaker notes",
      "blocks": [
        {
          "type": "text",
          "value": "Hello world!",
          "format": "h2"
        },
        {
          "type": "image",
          "value": "https://static.slid.es/images/screenshots/v1/slides-homepage-1440x900.png"
        },
        {
          "type": "iframe",
          "value": "https://slides.com/news/make-better-presentations/embed"
        },
        {
          "type": "table",
          "data": [
              ["A","B","C"],
              [ 1,  2,  3 ]
          ]
        }
      ]
    },
    {
      "background-image": "https://static.slid.es/images/screenshots/v1/slides-homepage-1440x900.png"
    },
    {
      "html": "<h1>HTML Slide</h1>"
    },
    {
      "markdown": "**Markdown** slide! <https://daringfireball.net/projects/markdown/syntax>"
    }
  ]
}

JSON Spec

[ "slide 1", ["slide 2.1", " slide 2.2" ], "slide 3" ]

{"foo": "bar"}

[
  ["A","B","C"],
  [ 1,  2,  3 ]
]