{ "cells": [ { "cell_type": "markdown", "metadata": { "slideshow": { "slide_type": "slide" } }, "source": [ "# Testing the overlay feature" ] }, { "cell_type": "markdown", "metadata": { "slideshow": { "slide_type": "-" } }, "source": [ "The overlay protocol goes like this" ] }, { "cell_type": "markdown", "metadata": { "slideshow": { "slide_type": "slide" } }, "source": [ "## Using `overlay` " ] }, { "cell_type": "markdown", "metadata": {}, "source": [ "If we find an `overlay` entry in your RISE config - this can be set in many different places, see [the customization doc](http://rise.readthedocs.io/en/latest/customize.html) -, then this string will be inserted in a `div#rise-overlay` element that shows on every slide.\n", "\n", "So this is a very low-level entry point, you are entirely responsible for providing a complete html fragment, and for styling it - how you can inject styling here is another story entirely, that is too covered [in the customization doc as well](http://rise.readthedocs.io/en/latest/customize.html#adding-custom-css)." ] }, { "cell_type": "markdown", "metadata": { "slideshow": { "slide_type": "slide" } }, "source": [ "## Using `header`, `footer` and `backimage`" ] }, { "cell_type": "markdown", "metadata": {}, "source": [ "If OTOH `overlay` cannot be found, then RISE looks for \n", "* `header`\n", "* `footer`\n", "* and `backimage` (again in the `RISE` config)" ] }, { "cell_type": "markdown", "metadata": { "slideshow": { "slide_type": "slide" } }, "source": [ "Then it creates an html element that looks like this\n", "\n", "```\n", "