deckroadmap adds section-aware roadmap footers to
Reveal.js presentations created with Quarto or R Markdown.
The goal is simple: help audiences understand where they are in the flow of a presentation. Instead of only knowing how many slides are left, they can see what has been covered, what section is active, and what comes next.
This vignette shows:
The workflow has two parts:
use_roadmap()data-roadmap valueA minimal example looks like this:
library(deckroadmap)
use_roadmap(
sections = c("Intro", "Problem", "Analysis", "Recommendation", "Next Steps")
)The function returns an HTML tag with the configuration and dependencies needed for the roadmap footer.
deckroadmap in QuartoIn a Quarto Reveal.js document, call use_roadmap() in an
R chunk near the top of the file.
A minimal example:
---
title: "deckroadmap Quarto demo"
format:
revealjs:
theme: default
---
``` r
library(deckroadmap)
use_roadmap(
c("Intro", "Problem", "Analysis", "Recommendation", "Next Steps"),
style = "progress",
active_bg_color = "#87CEEB"
)
```
## Welcome {data-roadmap="Intro"}
This is the opening slide.
## Why this matters {data-roadmap="Intro"}
Some framing content.
## The problem {data-roadmap="Problem"}
Describe the challenge here.
## What changed {data-roadmap="Problem"}
More problem context.
## Analysis overview {data-roadmap="Analysis"}
Start the analysis section.
## Key findings {data-roadmap="Analysis"}
Show results here.
## Recommendation {data-roadmap="Recommendation"}
Explain the recommendation.
## Tradeoffs {data-roadmap="Recommendation"}
Discuss caveats and decisions.
## Next steps {data-roadmap="Next Steps"}
End with the action plan.
## Q&A {data-roadmap="Next Steps"}
Questions.deckroadmap in R MarkdownThe same idea works for R Markdown Reveal.js slides.
---
title: "deckroadmap R Markdown demo"
output:
revealjs::revealjs_presentation
---
## Welcome {data-roadmap="Intro"}
This is the opening slide.
## Why this matters {data-roadmap="Intro"}
Some framing content.
## The problem {data-roadmap="Problem"}
Describe the challenge here.
## What changed {data-roadmap="Problem"}
More problem context.
## Analysis overview {data-roadmap="Analysis"}
Start the analysis section.
## Key findings {data-roadmap="Analysis"}
Show results here.
## Recommendation {data-roadmap="Recommendation"}
Explain the recommendation.
## Tradeoffs {data-roadmap="Recommendation"}
Discuss caveats and decisions.
## Next steps {data-roadmap="Next Steps"}
End with the action plan.
## Q&A {data-roadmap="Next Steps"}
Questions.The roadmap depends on slide-level section tags such as:
The values used in data-roadmap should match the section
names passed to use_roadmap().
For example, if the roadmap is defined as:
then valid slide tags include:
deckroadmap currently includes three built-in
styles.
The pill style is the default polished floating
footer.
The minimal style has less visual weight and works well
when you want simpler signposting.
You can customize font size, position, text colors, and, for the progress style, background colors.
Before rendering a full slide deck, you can preview a roadmap style
with preview_roadmap().
preview_roadmap(
sections = c("Intro", "Problem", "Analysis", "Recommendation", "Next Steps"),
current = "Analysis",
style = "progress"
)This is helpful when experimenting with styles, colors, and section names.
deckroadmap provides a simple way to add section-aware
roadmap footers to Reveal.js slides in Quarto and R Markdown. Define
your sections once, tag slides with data-roadmap, choose a
style, and optionally preview the result before rendering a full deck.
This small amount of structure can make it easier for audiences to
follow the flow of a presentation.