This commit add support for a new code-block delimiter that provides a simple way to inject any source code file found within the repo as a Markdown code-block on a presentation slide. The delimiter syntax looks as follows:
—?code=path/to/source/code.file
This commit also introduces support for code fragment highlighting. The CF-marker syntax, one or more of which must follow a code-block in your markdown, looks as follows:
@[fragment-range](optional-note)
Where fragment-range identifies a single line number, @[1], or a range of numbers, @[5-10]. The optional note is plain text that is displayed on the slide below the code-block when the fragment is in focus.
Web based printing to PDF is supported in Chrome only. This functionality is added to overcome differences between fonts available in the browser and the fonts available to decktape on the GitPitch server.
GitPitch default reveal.js dependency is now 3.4.1.
Also added support for new PITCHME.yaml property, called revealjs-version. This property allows a presentation owner to specify a specific version of reveal.js to use with their presentation.
Currently supported versions are 3.4.1 or 3.3.1.
A new parameter (p) on slideshow URLs accepts a relative path to a custom directory within a repo where PITCHME.* can be found for a given presentation. If (p) is not specified, the default behavior using the root directory within the repo is preserved.
This feature supports the creation and management of multiple presentations within a single repo (branch), potentially sharing common assets such as images, styles, etc.
The following changes were required to support this feature:
- Optional parameter (p) on slideshow urls
- Each (p) generates isolated print PDF
- Each (p) generates isolated offline ZIP
- Caching of YAML and Markdown is now (p) aware
