---
title: "Advanced Features"
output: rmarkdown::html_vignette
vignette: >
  %\VignetteIndexEntry{Advanced Features}
  %\VignetteEngine{knitr::rmarkdown}
  %\VignetteEncoding{UTF-8}
---

```{r, include = FALSE}
knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>",
  fig.width = 7,
  fig.height = 5
)
```

This vignette covers advanced dashboardr features: interactive inputs, data filtering, batch creation, survey weights, icons, and navigation customization.

<details>
<summary>📂 **Data Setup** (click to expand)</summary>

```{r setup, message=FALSE, warning=FALSE}
library(dashboardr)
library(dplyr)
library(gssr)
library(haven)

# Load GSS data
data(gss_all)

# Latest wave only (for most examples)
gss <- gss_all %>%
  select(year, age, sex, race, degree, happy, polviews, wtssps) %>%
  filter(year == max(year, na.rm = TRUE)) %>%
  filter(
    happy %in% 1:3,
    polviews %in% 1:7,
    !is.na(age), !is.na(sex), !is.na(race), !is.na(degree)
  ) %>%
  mutate(
    age = as.numeric(age),  # Keep age as numeric for filter comparisons
    happy = droplevels(as_factor(happy)),
    polviews = droplevels(as_factor(polviews)),
    degree = droplevels(as_factor(degree)),
    sex = droplevels(as_factor(sex)),
    race = droplevels(as_factor(race))
  )
```

</details>

```{r, include = FALSE}
library(dashboardr)
```

## 🔍 Filtering Data

Filters let you create multiple visualizations from the same dataset, each showing a different subset. Instead of manually splitting your data into separate data frames, you define the filter condition directly in `add_viz()`.

### Why Use Filters?

**Without filters**, you'd need to create separate datasets:

```r
# Tedious approach - don't do this
males <- gss %>% filter(sex == 1)
females <- gss %>% filter(sex == 2)

create_content(data = males, type = "bar") %>%
  add_viz(x_var = "happy", title = "Male")

create_content(data = females, type = "bar") %>%
  add_viz(x_var = "happy", title = "Female")
```

**With filters**, one dataset serves all visualizations:

```r
# Clean approach - do this!
create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "happy", title = "Male", filter = ~ sex == "male") %>%
  add_viz(x_var = "happy", title = "Female", filter = ~ sex == "female")
```

### Filter Syntax

Filters use R's formula syntax with a tilde (`~`). The expression after `~` is evaluated against your data:

| Filter | Meaning |
|--------|---------|
| `~ sex == 1` | Rows where sex equals 1 |
| `~ age > 30` | Rows where age is greater than 30 |
| `~ race == "white"` | Rows where race is "white" |
| `~ age >= 18 & age <= 35` | Rows where age is between 18 and 35 |
| `~ degree %in% c("bachelor", "graduate")` | Rows where degree is bachelor or graduate |

### Basic Example: Comparing Groups

Show the same variable for different subgroups side by side:

```{r}
filtered <- create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "happy", title = "Male", filter = ~ sex == "male", tabgroup = "Male") %>%
  add_viz(x_var = "happy", title = "Female", filter = ~ sex == "female", tabgroup = "Female")

print(filtered)
```

```{r}
filtered %>% preview()
```

This creates two charts in the same tabgroup - one filtered to males, one to females. Users can switch between them to compare happiness distributions.

### Complex Filters: Multiple Conditions

Combine conditions with `&` (and) and `|` (or). Here we create one tabgroup ("age_groups") with three tabs, each showing happiness for a different age range:

```{r}
complex <- create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "happy", title = "Young Adults (18-35)", 
          filter = ~ age >= 18 & age <= 35, tabgroup = "Youngsters") %>%
  add_viz(x_var = "happy", title = "Middle Age (36-55)", 
          filter = ~ age > 35 & age <= 55, tabgroup = "Middlers") %>%
  add_viz(x_var = "happy", title = "Older Adults (55+)", 
          filter = ~ age > 55, tabgroup = "Olders")

print(complex)
```

```{r}
complex %>% preview()
```

### Filters vs. group_var

**When to use `filter`:**
- You want completely separate charts for each group
- Groups need different titles, settings, or tabgroups
- You're comparing the same variable across subsets

**When to use `group_var`:**
- You want grouped bars within a single chart
- Direct visual comparison in one view

```{r}
# Using filter: separate charts per group
create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "happy", title = "Happiness (Male)", filter = ~ sex == "male", tabgroup = "separate") %>%
  add_viz(x_var = "happy", title = "Happiness (Female)", filter = ~ sex == "female", tabgroup = "separate") %>%
  preview()
```

```{r}
# Using group_var: one chart with grouped bars
create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "happy", group_var = "sex", title = "Happiness by Sex") %>%
  preview()
```

### Filter + title_tabset: Organized Comparisons

When you're comparing the **same variable across multiple groups**, `title_tabset` creates a second level of tabs:

- `tabgroup` = the **category** (e.g., "Happiness", "Education")
- `title_tabset` = the **variant** within that category (e.g., "Male", "Female")

```{r}
gender_comparison <- create_content(data = gss, type = "bar") %>%
  # Happiness tabgroup with Male/Female sub-tabs
  add_viz(x_var = "happy", title = "Happiness", 
          filter = ~ sex == "male", title_tabset = "Male", tabgroup = "happiness") %>%
  add_viz(x_var = "happy", title = "Happiness", 
          filter = ~ sex == "female", title_tabset = "Female", tabgroup = "happiness") %>%
  # Education tabgroup with Male/Female sub-tabs
  add_viz(x_var = "degree", title = "Education", 
          filter = ~ sex == "male", title_tabset = "Male", tabgroup = "education") %>%
  add_viz(x_var = "degree", title = "Education", 
          filter = ~ sex == "female", title_tabset = "Female", tabgroup = "education")

print(gender_comparison)
```

```{r}
gender_comparison %>% preview()
```

## 📚 Batch Creation with add_vizzes()

When you need to create many similar visualizations, `add_vizzes()` lets you do it in one call instead of repeating `add_viz()` multiple times.

### The Problem: Repetitive Code

```r
# Tedious and error-prone
create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "degree", title = "Education", tabgroup = "survey") %>%
  add_viz(x_var = "race", title = "Race", tabgroup = "survey") %>%
  add_viz(x_var = "happy", title = "Happiness", tabgroup = "survey") %>%
  add_viz(x_var = "polviews", title = "Politics", tabgroup = "survey")
```

### The Solution: Vector Parameters

With `add_vizzes()`, pass vectors for the parameters that vary, and single values for parameters that stay the same:

```{r}
vars <- c("degree", "race", "happy", "polviews")
labels <- c("Education", "Race", "Happiness", "Politics")

batch <- create_content(data = gss, type = "bar") %>%
  add_vizzes(x_var = vars, title = labels, tabgroup = "survey")

print(batch)
```

```{r}
batch %>% preview()
```

### How It Works

**Vector parameters** (vary per visualization):
- `x_var`, `y_var`, `stack_var`, `group_var`, `title`, `questions`
- Must all have the same length

**Scalar parameters** (shared across all):
- `type`, `color_palette`, `bar_type`, `horizontal`, `tabgroup` (if single value), etc.
- Applied to every visualization

### Different Tabgroups Per Viz

Pass `tabgroup` as a vector to put each visualization in a different tab:

```{r}
create_content(data = gss, type = "bar") %>%
  add_vizzes(
    x_var = c("degree", "happy", "polviews"),
    title = c("Education", "Happiness", "Politics"),
    tabgroup = c("demographics", "wellbeing", "attitudes")
  ) %>%
  preview()
```



## 🎚️ Interactive Inputs

Interactive input widgets transform your dashboard from a static report into an **exploratory data tool**. Users can filter data, adjust parameters, and see visualizations update in real-time.

> **🔗 See it in action:** Check out the [Inputs Demo](../live-demos/inputs/index.html) to try all input types with real GSS data!

### How Inputs Work

The input system connects **user controls** to **data columns**:

```
User selects "Bachelor's" in dropdown
        ↓
filter_var = "degree" tells dashboardr which column to filter
        ↓
Data is filtered to rows where degree == "Bachelor's"
        ↓
All visualizations on the page update automatically
```

**Basic pattern:**

```r
create_page("Analysis", data = my_data, type = "bar") %>%
  add_input_row() %>%
    add_input(input_id = "edu", label = "Education", 
              filter_var = "degree", options_from = "degree") %>%
  end_input_row() %>%
  add_viz(x_var = "happy", title = "Happiness")  # Automatically filtered!
```

> **Note:** Inputs show as placeholders in `preview()`. They become fully interactive when you run `generate_dashboard(render = TRUE)` and view in a browser.

### Input Types

| Type | Best For | Selection |
|------|----------|-----------|
| `select_multiple` | Many categories (10+) | Multiple |
| `select_single` | Many categories, pick one | Single |
| `checkbox` | Few categories (3-6) | Multiple |
| `radio` | Mutually exclusive choices | Single |
| `slider` | Numeric ranges or ordered categories | Single value |
| `switch` | Toggle a series on/off | Boolean |

### Select Dropdowns

```{r, eval=FALSE}
# Single selection
add_input(
  input_id = "metric",
  label = "Select Metric",
  type = "select_single",
  filter_var = "metric",
  options = c("Sales", "Revenue", "Profit"),
  default_selected = "Sales"
)

# Multiple selection
add_input(
  input_id = "countries",
  label = "Select Countries",
  type = "select_multiple",
  filter_var = "country",
  options_from = "country",  # Get options from data column
  placeholder = "Choose countries..."
)
```

#### Grouped Options

For long lists, organize options into groups:

```{r, eval=FALSE}
# Create grouped options (named list)
countries_by_region <- list(
  "Europe" = c("Germany", "France", "UK", "Spain"),
  "Asia" = c("China", "Japan", "India", "Korea"),
  "Americas" = c("USA", "Canada", "Brazil", "Mexico")
)

add_input(
  input_id = "country",
  label = "Select Country",
  type = "select_multiple",
  filter_var = "country",
  options = countries_by_region,  # Grouped!
  default_selected = c("USA", "Germany")
)
```

### Checkbox & Radio Buttons

```{r, eval=FALSE}
# Checkboxes - multiple selection, all visible
add_input(
  input_id = "race",
  label = "Race",
  type = "checkbox",
  filter_var = "race",
  options_from = "race",
  inline = TRUE  # Horizontal layout
)

# Radio buttons - single selection
add_input(
  input_id = "sex",
  label = "Gender",
  type = "radio",
  filter_var = "sex",
  options_from = "sex",
  inline = TRUE
)
```

### Sliders

Sliders work for numeric data or ordered categories:
```{r, eval=FALSE}
# Numeric slider
add_input(
  input_id = "year",
  label = "Year",
  type = "slider",
  filter_var = "year",
  min = 2010,
  max = 2024,
  step = 1,
  value = 2020,
  show_value = TRUE
)

# Slider with custom labels (for ordered categories)
add_input(
  input_id = "decade",
  label = "Starting Decade",
  type = "slider",
  filter_var = "decade",
  min = 1,
  max = 6,
  step = 1,
  value = 1,
  labels = c("1970s", "1980s", "1990s", "2000s", "2010s", "2020s")
)
```

### Switch (Toggle Series)
Switches toggle a specific data series on/off. Unlike other inputs that filter data, a switch with `toggle_series` controls visibility of a named series in your chart:

```{r, eval=FALSE}
add_input(
  input_id = "show_avg",
  label = "Show Global Average",
  type = "switch",
  filter_var = "country",
  toggle_series = "Global Average",  # Must match a value in your data
  value = TRUE,  # Start with it shown
  override = TRUE
)
```

### Input Layout

Use `add_input_row()` to organize inputs horizontally:

```{r, eval=FALSE}
create_page("Analysis", data = gss, type = "bar") %>%
  # First row: main filters
  add_input_row(style = "inline", align = "center") %>%
    add_input(input_id = "edu", label = "Education", 
              filter_var = "degree", options_from = "degree",
              width = "300px") %>%
    add_input(input_id = "race", label = "Race",
              type = "checkbox", filter_var = "race", 
              options_from = "race", inline = TRUE) %>%
  end_input_row() %>%
  # Second row: additional controls
  add_input_row() %>%
    add_input(input_id = "sex", label = "Gender",
              type = "radio", filter_var = "sex",
              options_from = "sex", inline = TRUE) %>%
  end_input_row() %>%
  add_viz(x_var = "happy", title = "Happiness Distribution")
```

### Input Parameters Reference

| Parameter | Description | Used With |
|-----------|-------------|-----------|
| `input_id` | Unique identifier | All |
| `label` | Display label | All |
| `type` | Input type | All |
| `filter_var` | Column to filter | All |
| `options` | Manual list of options | select, checkbox, radio |
| `options_from` | Column to get options from | select, checkbox, radio |
| `default_selected` | Pre-selected values | select, checkbox, radio |
| `min`, `max`, `step` | Range settings | slider |
| `value` | Default value | slider, switch |
| `labels` | Custom labels for slider positions | slider |
| `toggle_series` | Series name to show/hide | switch |
| `override` | Override other filters | switch |
| `inline` | Horizontal layout | checkbox, radio |
| `width` | Input width (CSS) | select |
| `placeholder` | Placeholder text | select |
| `help` | Help text below input | All |

### Complete Example

Here's a full working example with multiple input types:

```{r, eval=FALSE}
library(dashboardr)
library(dplyr)
library(gssr)
library(haven)

# Prepare data
data(gss_all)
gss_inputs <- gss_all %>%
  select(year, age, sex, race, degree, happy, polviews) %>%
  filter(year >= 2010, happy %in% 1:3,
         !is.na(age), !is.na(sex), !is.na(race), !is.na(degree)) %>%
  mutate(across(c(happy, degree, sex, race), ~droplevels(as_factor(.))))

# Create page with inputs
inputs_page <- create_page("Explorer", data = gss_inputs, type = "bar") %>%
  add_text(
    "## GSS Data Explorer",
    "",
    "Filter the data using the controls below. All charts update automatically."
  ) %>%
  add_input_row() %>%
    add_input(
      input_id = "edu",
      label = "Education Level",
      type = "select_multiple",
      filter_var = "degree",
      options_from = "degree",
      width = "250px"
    ) %>%
    add_input(
      input_id = "race",
      label = "Race",
      type = "checkbox",
      filter_var = "race",
      options_from = "race",
      inline = TRUE
    ) %>%
  end_input_row() %>%
  add_input_row() %>%
    add_input(
      input_id = "sex",
      label = "Gender",
      type = "radio",
      filter_var = "sex",
      options_from = "sex",
      inline = TRUE
    ) %>%
  end_input_row() %>%
  add_viz(x_var = "happy", title = "Happiness", tabgroup = "Results") %>%
  add_viz(x_var = "polviews", title = "Political Views", tabgroup = "Results")

# Generate
create_dashboard(title = "GSS Explorer", output_dir = "gss_explorer") %>%
  add_pages(inputs_page) %>%
  generate_dashboard(render = TRUE, open = "browser")
```


## 📋 Page Sidebars

Sidebars provide a dedicated space for inputs and controls alongside your visualizations. Instead of placing filters above your charts, a sidebar keeps them visible and accessible as users scroll through content.

### Why Use Sidebars?

- **Persistent controls**: Filters remain visible while scrolling through charts
- **Better space usage**: Inputs don't take up vertical space in the main content area
- **Professional look**: Common pattern in data dashboards and analytics tools
- **Mobile-friendly**: Automatically adapts to smaller screens

### Basic Sidebar

Use `add_sidebar()` and `end_sidebar()` to wrap sidebar content:
```{r, eval=FALSE}
page <- create_page("Analysis", data = gss) %>%
  create_content(data = gss) %>%
  add_sidebar(width = "280px", title = "Filters") %>%
    add_text("Filter the data below.") %>%
    add_divider() %>%
    add_input(
      input_id = "edu_filter",
      label = "Education:",
      type = "checkbox",
      filter_var = "degree",
      options_from = "degree",
      columns = 2  # Display in 2-column grid
    ) %>%
  end_sidebar() %>%
  add_viz(type = "bar", x_var = "happy", title = "Happiness Distribution")
```

### Sidebar Position

By default, sidebars appear on the left. Use `position = "right"` for a right-side sidebar:

```{r, eval=FALSE}
create_content(data = gss) %>%
  add_sidebar(width = "300px", title = "Options", position = "right") %>%
    add_input(...) %>%
  end_sidebar() %>%
  add_viz(...)
```

### Sidebar Content

Sidebars can contain any content, not just inputs:

```{r, eval=FALSE}
add_sidebar(width = "280px", title = "About") %>%
  add_text("Select options to explore the data.") %>%
  add_divider() %>%
  add_input(...) %>%
  add_spacer(height = "1rem") %>%
  add_callout("Data source: GSS 2022", type = "note") %>%
  add_badge("Updated Weekly", color = "primary") %>%
end_sidebar()
```

### Multi-Column Inputs

For checkboxes and radio buttons, use the `columns` parameter to display options in a grid layout instead of a vertical list:

```{r, eval=FALSE}
# 2-column grid (great for sidebars)
add_input(
  input_id = "countries",
  label = "Countries:",
  type = "checkbox",
  filter_var = "country",
  options = c("USA", "UK", "Germany", "France", "Italy"),
  columns = 2
)

# 3-column grid (for wider sidebars)
add_input(..., columns = 3)

# Inline (horizontal wrap)
add_input(..., inline = TRUE)
```

### Different Sidebars Per Page

Each page can have its own sidebar with different inputs:

```{r, eval=FALSE}
# Page 1: Left sidebar with checkboxes
page1 <- create_page("Demographics", data = gss) %>%
  create_content(data = gss) %>%
  add_sidebar(width = "280px", title = "Filter") %>%
    add_input(type = "checkbox", ...) %>%
  end_sidebar() %>%
  add_viz(...)

# Page 2: Right sidebar with dropdown
page2 <- create_page("Trends", data = gss) %>%
  create_content(data = gss) %>%
  add_sidebar(width = "300px", position = "right", title = "Options") %>%
    add_input(type = "select_multiple", ...) %>%
  end_sidebar() %>%
  add_viz(...)

# Page 3: No sidebar
page3 <- create_page("About") %>%
  add_text("About this dashboard...")
```

### Complete Example

```{r, eval=FALSE}
library(dashboardr)

# Create page with sidebar
page <- create_page("Explorer", data = gss) %>%
  create_content(data = gss, type = "bar") %>%
  add_sidebar(width = "280px", title = "Data Filters") %>%
    add_text("Select groups to include in the analysis.") %>%
    add_divider() %>%
    add_input(
      input_id = "degree_filter",
      label = "Education Level:",
      type = "checkbox",
      filter_var = "degree",
      options_from = "degree",
      columns = 2
    ) %>%
    add_spacer(height = "0.5rem") %>%
    add_input(
      input_id = "sex_filter",
      label = "Gender:",
      type = "radio",
      filter_var = "sex",
      options_from = "sex"
    ) %>%
    add_divider() %>%
    add_callout("Charts update automatically when you change filters.", type = "tip") %>%
  end_sidebar() %>%
  add_viz(x_var = "happy", title = "Happiness", tabgroup = "Results") %>%
  add_viz(x_var = "polviews", title = "Political Views", tabgroup = "Results")

# Generate dashboard
create_dashboard(title = "GSS Explorer", output_dir = "gss_sidebar") %>%
  add_page(page) %>%
  generate_dashboard(render = TRUE)
```

### Sidebar Parameters

| Parameter | Description | Default |
|-----------|-------------|---------|
| `width` | Sidebar width (CSS units) | `"280px"` |
| `title` | Heading text at top of sidebar | `NULL` |
| `position` | `"left"` or `"right"` | `"left"` |

### Mobile Behavior

On mobile devices (screens < 768px wide), sidebars automatically:

- Stack above/below the main content instead of beside it
- Take full width of the screen
- Maintain all functionality

## 🔄 Cross-Tab Filtering & Dynamic Titles

For sidebar dashboards where inputs control multiple visualizations, dashboardr supports **client-side cross-tab filtering** — charts rebuild instantly without server round-trips.

> **🔗 See it in action:** Check out the [GSS Explorer Demo](../live-demos/sidebar-gss/index.html) to see cross-tab filtering, conditional visibility, dynamic titles, and consistent colors all working together!

### Conditional Visibility with show_when

Use `show_when` to show or hide a visualization based on the current sidebar input values. This lets you display different chart types depending on user selections:

```{r, eval=FALSE}
# Show a stacked bar for single-year views
add_viz(
  type      = "stackedbar",
  x_var     = "response",
  stack_var = "group",
  y_var     = "n",
  show_when = ~ time_period %in% c("2022", "2024") & breakdown != "Overall"
)

# Show a timeline for the "Over Time" view
add_viz(
  type     = "timeline",
  time_var = "year",
  y_var    = "score",
  show_when = ~ time_period == "Over Time"
)
```

The `show_when` formula uses the same operators as R: `==`, `!=`, `%in%`, combined with `&` (and) and `|` (or). Hidden charts fully collapse — no empty space left behind.

### Dynamic Titles with Placeholders

Chart titles can include `{placeholder}` tokens that are automatically replaced with the current sidebar input value:

```{r, eval=FALSE}
add_viz(
  type  = "stackedbar",
  title = "{dimension}: {question} by {breakdown} ({time_period})",
  ...
)
```

When the user selects "Race" in the sidebar, `{breakdown}` becomes "Race" in the title. Placeholders are matched by `input_id`.

### Derived Placeholders with title_map

Sometimes you need a placeholder whose value is *derived* from an input — not the input value itself. For example, showing which response value is tracked in a timeline (e.g., "Legal" for marijuana, "Favor" for death penalty).

Use `title_map` with a simple named vector:

```{r, eval=FALSE}
# Pre-compute the mapping from your existing objects
key_response_map <- setNames(key_resp[question_var], names(question_var))
# Result: c("Marijuana Legalization" = "Legal", "Death Penalty" = "Favor", ...)

add_viz(
  type      = "timeline",
  title     = "{question}: % responding '{key_response}' by {breakdown}",
  title_map = list(key_response = key_response_map),
  ...
)
```

The system auto-detects which sidebar input the mapping corresponds to — you just provide the named vector. When the user selects "Marijuana Legalization", `{key_response}` becomes "Legal".

### Consistent Colors with Named color_palette

By default, Highcharts assigns colors positionally. When stacked bars and timelines add series in different orders, the same group gets different colors. Fix this with a **named** `color_palette`:

```{r, eval=FALSE}
# Define once
group_colors <- c(
  "Male" = "#F28E2B", "Female" = "#E15759",
  "White" = "#EDC948", "Black" = "#59A14F", "Other" = "#76B7B2",
  "18-29" = "#BAB0AC", "30-44" = "#9C755F", "45-59" = "#FF9DA7", "60+" = "#B07AA1"
)

# Use in both charts — "Male" is always #F28E2B
add_viz(type = "stackedbar", color_palette = group_colors, ...)
add_viz(type = "timeline", color_palette = group_colors, ...)
```

Named palettes map colors by series name. Unnamed vectors (`c("#F28E2B", "#E15759")`) still work as positional cycles for backwards compatibility.

### Series Ordering with group_order

Control the order series appear in timeline charts:

```{r, eval=FALSE}
add_viz(
  type        = "timeline",
  group_var   = "breakdown_value",
  group_order = c("Male", "Female", "White", "Black", "Other"),
  ...
)
```

This ensures the legend and series order matches across chart types. Use `rev()` if the visual order needs to be reversed to match a horizontal stacked bar's legend.

### Complete Sidebar Example

```{r, eval=FALSE}
library(dashboardr)

# Define color and order vectors
all_groups <- c("All", "Male", "Female", "White", "Black", "Other")
group_colors <- c(
  "All" = "#4E79A7", "Male" = "#F28E2B", "Female" = "#E15759",
  "White" = "#EDC948", "Black" = "#59A14F", "Other" = "#76B7B2"
)

explorer <- create_content(data = page_data) %>%
  add_sidebar(width = "250px", title = "Controls") %>%
    add_input(input_id = "question", label = "Question",
              type = "radio", filter_var = "question",
              options = c("Trust", "Fairness")) %>%
    add_input(input_id = "breakdown", label = "Compare by",
              type = "radio", filter_var = "breakdown_type",
              options = c("Overall", "Sex", "Race")) %>%
  end_sidebar() %>%
  add_viz(
    type          = "stackedbar",
    x_var         = "response",
    stack_var     = "breakdown_value",
    y_var         = "n",
    title         = "{question} by {breakdown}",
    color_palette = group_colors,
    stack_order   = all_groups,
    show_when     = ~ breakdown != "Overall"
  ) %>%
  add_viz(
    type          = "timeline",
    time_var      = "year",
    y_var         = "score",
    group_var     = "breakdown_value",
    agg           = "none",
    title         = "{question}: trend by {breakdown}",
    color_palette = group_colors,
    group_order   = rev(all_groups),
    show_when     = ~ time_period == "Over Time"
  )
```

## ⚖️ Survey Weights

Survey data often requires weighting to produce population-representative estimates. Without weights, your sample might over- or under-represent certain groups.

### Why Use Weights?

**Unweighted data** shows your raw sample distribution - useful for understanding who responded, but may not reflect the actual population.

**Weighted data** adjusts for sampling design and non-response, giving you estimates that better represent the target population.

### Applying Weights

Set `weight_var` in `create_content()` to apply weights to all visualizations. The GSS provides several weight variables; `wtssps` is the recommended post-stratification weight for recent years:

```{r}
# Compare unweighted vs weighted
unweighted <- create_content(data = gss, type = "bar") %>%
  add_viz(x_var = "degree", title = "Education (Unweighted)", tabgroup = "comparison")

weighted <- create_content(data = gss, type = "bar", weight_var = "wtssps") %>%
  add_viz(x_var = "degree", title = "Education (Weighted)", tabgroup = "comparison")

# Combine to see the difference
(unweighted + weighted) %>% preview()
```

Notice how the distributions differ - the weighted version adjusts for the fact that more educated people are typically overrepresented in survey samples.

### Weight as a Default

When you set `weight_var` in `create_content()`, it applies to **all** visualizations in that collection:

```{r}
# All three charts use the same weight
weighted_collection <- create_content(data = gss, type = "bar", weight_var = "wtssps") %>%
  add_viz(x_var = "degree", title = "Education", tabgroup = "weighted") %>%
  add_viz(x_var = "race", title = "Race", tabgroup = "weighted") %>%
  add_viz(x_var = "happy", title = "Happiness", tabgroup = "weighted")

print(weighted_collection)
```

```{r}
weighted_collection %>% preview()
```

## 🎯 Customizing Tooltips

dashboardr provides a flexible 3-tier system for customizing chart tooltips, from quick tweaks to full control.

### Quick Customization (Tier 1)

Add prefix or suffix text to tooltip values:

```{r, eval=FALSE}
viz_bar(data = gss, x_var = "degree", 
        tooltip_prefix = "Count: ",
        tooltip_suffix = " respondents")
```

### Format Strings (Tier 2)

Use format strings with `{placeholders}` for more control:
```{r, eval=FALSE}
viz_bar(data = gss, x_var = "degree", 
        tooltip = "{category}: {value} people ({percent})")
```

Available placeholders vary by chart type:

| Placeholder | Description | Charts |
|-------------|-------------|--------|
| `{value}` | Primary value | All |
| `{category}` | X-axis category | bar, histogram, stackedbar |
| `{x}`, `{y}` | Coordinates | scatter, heatmap |
| `{series}` | Series name | Grouped charts |
| `{percent}` | Percentage | Percent-type charts |
| `{name}` | Point name | All |

### Full Control (Tier 3)

Use the `tooltip()` helper for complete customization including styling:

```{r, eval=FALSE}
viz_bar(data = gss, x_var = "degree",
        tooltip = tooltip(
          format = "<b>{category}</b><br/>Count: {value}",
          backgroundColor = "#f8f9fa",
          borderColor = "#dee2e6",
          borderRadius = 8,
          style = list(fontSize = "14px")
        ))
```

The `tooltip()` function exposes all Highcharts tooltip options:

- `format` - Format string with {placeholders}
- `shared` - Share tooltip across series (TRUE/FALSE)
- `backgroundColor`, `borderColor`, `borderRadius` - Visual styling
- `style` - CSS styles as a named list
- `header` - Header format (use FALSE to hide)
- `enabled` - Enable/disable tooltips entirely

All chart functions (`viz_bar()`, `viz_scatter()`, `viz_histogram()`, etc.) support the same tooltip parameters for consistent behavior across your dashboard.

## 🎨 Icons

dashboardr uses [Iconify](https://icon-sets.iconify.design/) for **200,000+ icons** from 100+ icon sets.

### Icon Format

Icons use the format `set:icon-name`:

```r
icon = "ph:house-fill"       # Phosphor Icons
icon = "mdi:chart-line"      # Material Design Icons
icon = "bi:graph-up"         # Bootstrap Icons
```

### Popular Icon Sets

| Set | Prefix | Style | Examples |
|-----|--------|-------|----------|
| [Phosphor](https://phosphoricons.com/) | `ph:` | Clean, modern | `ph:chart-line`, `ph:users-fill`, `ph:gear-fill` |
| [Material Design](https://icon-sets.iconify.design/mdi/) | `mdi:` | Google style | `mdi:chart-bar`, `mdi:account-group` |
| [Bootstrap](https://icons.getbootstrap.com/) | `bi:` | Bootstrap style | `bi:graph-up`, `bi:people-fill` |
| [Font Awesome](https://fontawesome.com/) | `fa:` | Classic | `fa:chart-bar`, `fa:users` |

### Page Icons

Add icons to pages in the navbar:

```{r, eval=FALSE}
create_page("Home", icon = "ph:house-fill")
create_page("Analysis", icon = "ph:chart-bar-fill")
create_page("Settings", icon = "ph:gear-fill", navbar_align = "right")
```

### Tabgroup Icons

Add icons to tab labels using Quarto shortcodes:
<!-- Comment to prevent knitr from processing the iconify shortcode -->

```{r, eval=FALSE}
viz <- create_content(type = "bar") %>%
  add_viz(x_var = "age", tabgroup = "demographics") %>%
  add_viz(x_var = "income", tabgroup = "financial") %>%
  set_tabgroup_labels(
    demographics = "{{< iconify ph:users-fill >}} Demographics",
    financial = "{{< iconify ph:currency-dollar >}} Financial"
  )
```

### Icons in Text

Use Quarto shortcodes in markdown text:

```{r, eval=FALSE}
add_text(
  "## Features {{< iconify ph:sparkle-fill >}}",
  "",
  "- {{< iconify ph:check-circle-fill >}} Easy to use",
  "- {{< iconify ph:lightning-fill >}} Fast performance",
  "- {{< iconify ph:heart-fill >}} Beautiful design"
)
```

### Finding Icons

1. Visit [Iconify Icon Sets](https://icon-sets.iconify.design/)
2. Search for what you need (e.g., "chart", "user", "settings")
3. Click an icon to see its name
4. Use it as `set:icon-name`

**Common choices by purpose:**

| Purpose | Recommended Icons |
|---------|-------------------|
| Home/Landing | `ph:house-fill`, `ph:home` |
| Charts/Analysis | `ph:chart-line`, `ph:chart-bar-fill`, `ph:graph` |
| Users/Demographics | `ph:users-fill`, `ph:user-circle` |
| Settings/Config | `ph:gear-fill`, `ph:sliders` |
| Info/About | `ph:info-fill`, `ph:question` |
| Download/Export | `ph:download-simple`, `ph:export` |
| Time/Trends | `ph:clock`, `ph:trend-up` |

### Best Practice: Consistency

Pick one icon set and stick with it throughout your dashboard:

```{r, eval=FALSE}
# Good: All Phosphor icons
create_page("Home", icon = "ph:house-fill")
create_page("Analysis", icon = "ph:chart-line")
create_page("About", icon = "ph:info-fill")

# Avoid: Mixed icon sets (inconsistent visual style)
create_page("Home", icon = "ph:house-fill")
create_page("Analysis", icon = "bi:graph-up")     # Different set
create_page("About", icon = "mdi:information")    # Another set
```

## 🪟 Modals

Modals are popup overlays that display additional content without navigating away from the current page. They're perfect for showing detailed explanations, images, data tables, or supplementary information that users can access on demand.

### Why Use Modals?

- **Contextual information**: Show detailed explanations for chart elements without cluttering the main view
- **Image galleries**: Display full-size images when users click on thumbnails
- **Data tables**: Show raw data or methodology details on demand
- **Progressive disclosure**: Keep the main page clean while making details available

### Basic Modal Usage

Creating a modal requires two parts:
1. A **trigger link** that users click
2. The **modal content** that appears in the popup

Use `add_modal()` in your content pipeline, then reference it with a markdown link:

```{r, eval=FALSE}
content <- create_content() %>%
  add_text(
    "## Survey Results",
    "",
    "The response rate was 78%. [View methodology](#methodology){.modal-link}"
  ) %>%
  add_modal(
    modal_id = "methodology",
    title = "Survey Methodology",
    modal_content = "Data was collected via online questionnaire from March 1-15, 2024. 
                     The sample was weighted to match national demographics."
  )
```

The `{.modal-link}` class on the markdown link tells dashboardr to open the content as a modal instead of navigating to a new page.

### Modal with Image

Show images in a modal - great for displaying full-size charts, diagrams, or photos:

```{r, eval=FALSE}
content <- create_content() %>%
  add_text("[View the survey question](#question-img){.modal-link}") %>%
  add_modal(
    modal_id = "question-img",
    title = "Question Wording",
    image = "question_screenshot.png",
    image_width = "80%",  # Control the image size
    modal_content = "Respondents were shown this question as part of the survey."
  )
```

### Modal with Data Table

Pass a data.frame directly and it will be automatically converted to an HTML table:

```{r, eval=FALSE}
# Show summary statistics in a modal
summary_data <- data.frame(
  Metric = c("Mean", "Median", "SD", "N"),
  Value = c(3.42, 3.5, 1.23, 1247)
)

content <- create_content() %>%
  add_text("[View summary statistics](#stats){.modal-link}") %>%
  add_modal(
    modal_id = "stats",
    title = "Summary Statistics",
    modal_content = summary_data
  )
```

### Modal Parameters

| Parameter | Description | Example |
|-----------|-------------|---------|
| `modal_id` | Unique identifier (used in link) | `"details"`, `"chart-info"` |
| `title` | Heading displayed at top of modal | `"More Information"` |
| `modal_content` | Text, HTML, or data.frame | `"Description..."` or `my_df` |
| `image` | Path or URL to an image | `"images/chart.png"` |
| `image_width` | Width of the image | `"100%"`, `"70%"`, `"500px"` |

### Multiple Modals on One Page

You can add as many modals as needed - just ensure each has a unique `modal_id`:

```{r, eval=FALSE}
content <- create_content() %>%
  add_text(
    "## Results Overview",
    "",
    "- Demographics: [see details](#demo-modal){.modal-link}",
    "- Methodology: [see details](#method-modal){.modal-link}",
    "- Limitations: [see details](#limits-modal){.modal-link}"
  ) %>%
  add_modal(
    modal_id = "demo-modal",
    title = "Demographics",
    modal_content = "Sample was 52% female, median age 42..."
  ) %>%
  add_modal(
    modal_id = "method-modal", 
    title = "Methodology",
    modal_content = "Online panel survey conducted..."
  ) %>%
  add_modal(
    modal_id = "limits-modal",
    title = "Limitations",
    modal_content = "This study has several limitations..."
  )
```

### Complete Example

Here's a full example showing modals used with visualizations:

```{r, eval=FALSE}
library(dashboardr)
library(dplyr)

# Create page with charts and modals for additional context
results_page <- create_page("Results", data = gss, type = "bar") %>%
  add_text(
    "## Survey Results",
    "",
    "These charts show key findings from our analysis.",
    "[Learn about our methodology](#methodology){.modal-link}"
  ) %>%
  add_viz(
    x_var = "happy",
    title = "Happiness Distribution",
    tabgroup = "findings"
  ) %>%
  add_text(
    "",
    "[View the original survey question](#question){.modal-link}"
  ) %>%
  add_modal(
    modal_id = "methodology",
    title = "Survey Methodology",
    modal_content = "<p>Data from the General Social Survey (GSS), a nationally 
                     representative survey of US adults conducted since 1972.</p>
                     <p>Weights were applied to adjust for sampling design.</p>"
  ) %>%
  add_modal(
    modal_id = "question",
    title = "Survey Question",
    image = "happiness_question.png",
    image_width = "70%",
    modal_content = "Respondents were asked: 'Taken all together, how would you 
                     say things are these days - would you say that you are very happy, 
                     pretty happy, or not too happy?'"
  )

# Generate the dashboard
create_dashboard(title = "GSS Analysis", output_dir = "gss_modals") %>%
  add_page(results_page) %>%
  generate_dashboard(render = TRUE)
```

### Low-Level Modal Functions

For more control, you can use the underlying helper functions directly:

- `enable_modals()` - Adds the CSS/JS for modal functionality
- `modal_link(text, modal_id)` - Creates a clickable link
- `modal_content(modal_id, ...)` - Creates the modal container

```{r, eval=FALSE}
# Using low-level functions (rarely needed)
library(htmltools)

# In a Quarto/R Markdown document:
enable_modals()

# Create a link
modal_link("Click for details", "my-modal", class = "btn btn-primary")

# Create the modal content
modal_content(
  modal_id = "my-modal",
  title = "Details",
  image = "chart.png",
  text = "This chart shows..."
)
```

Most users should stick with `add_modal()` in their pipelines for a cleaner workflow.

## 🧭 Navbar Customization

The navbar is the main navigation bar at the top of your dashboard. You can customize it extensively to add dropdown menus, external links, and control how pages are arranged.

### Dropdown Menus

Dropdown menus let you organize related links or pages under a single menu item. This is useful when you have many pages or want to include quick links to downloads, documentation, or related resources.

Use `navbar_left` to place menus on the left side of the navbar, or `navbar_right` for the right side. Each menu item is a list with:

- **`text`**: The label shown in the navbar
- **`menu`**: A list of sub-items, each with `text` and `href`
- **`"---"`**: Creates a visual divider between menu items

```{r, eval=FALSE}
create_dashboard(
  title = "My Dashboard",
  output_dir = "output",
  navbar_left = list(
    list(
      text = "Analysis",
      menu = list(
        list(text = "Demographics", href = "demographics.html"),
        list(text = "Trends", href = "trends.html"),
        list(text = "---"),  # Divider
        list(text = "Download Data", href = "data.csv")
      )
    )
  )
)
```

### External Links

Add links to external resources like GitHub repositories, documentation sites, or data sources. These appear as clickable items in the navbar and open in a new tab when clicked.

Each link can include:

- **`text`**: The visible label
- **`href`**: The URL (can be internal `.html` pages or external `https://` URLs)
- **`icon`**: An optional Iconify icon code (see the Icons section for available icons)

```{r, eval=FALSE}
create_dashboard(
  title = "My Dashboard",
  output_dir = "output",
  navbar_right = list(
    list(text = "GitHub", href = "https://github.com/org/repo", icon = "ph:github-logo"),
    list(text = "Documentation", href = "https://docs.example.com")
  )
)
```

### Sidebar Navigation

For dashboards with many pages (10+), consider using sidebar navigation instead of the top navbar. The sidebar provides more vertical space for page links and can include hierarchical organization.

Available sidebar options:

| Parameter | Description |
|-----------|-------------|
| `sidebar = TRUE` | Enable sidebar navigation |
| `sidebar_title` | Title shown at the top of the sidebar |
| `sidebar_style` | `"floating"` (overlays content) or `"docked"` (pushes content) |

```{r, eval=FALSE}
create_dashboard(
  title = "My Dashboard",
  output_dir = "output",
  sidebar = TRUE,
  sidebar_title = "Navigation",
  sidebar_style = "floating"  # or "docked"
)
```

> **Tip:** Sidebar navigation works especially well on mobile devices where horizontal navbar space is limited.

### Page Alignment

By default, all pages appear on the left side of the navbar. You can move specific pages to the right side using `navbar_align = "right"`. This is a common pattern for utility pages like "About", "Settings", or "Help" that users access less frequently.

```{r, eval=FALSE}
home <- create_page("Home", icon = "ph:house-fill")
analysis <- create_page("Analysis", icon = "ph:chart-bar-fill")
about <- create_page("About", icon = "ph:info-fill", navbar_align = "right")
settings <- create_page("Settings", icon = "ph:gear-fill", navbar_align = "right")

create_dashboard(title = "My Dashboard") %>%
  add_pages(home, analysis, about, settings)
```

The resulting navbar will show: `Home | Analysis` on the left, and `About | Settings` on the right.

## 🎨 Tab Styling

Customize the appearance of tabs within your pages using `tabset_theme` and `tabset_colors`. Tab styling affects how tabbed content (created via `tabgroup`) appears to users.

### Available Themes

Four built-in themes provide different visual styles for your tabs. Each theme changes the shape, spacing, and general appearance of the tab buttons.

| Theme | Description | Best For |
|-------|-------------|----------|
| `"default"` | Standard Quarto tabs with underline indicator | General use, compatibility |
| `"modern"` | Clean look with subtle backgrounds | Professional dashboards |
| `"pills"` | Rounded pill-shaped buttons | Friendly, approachable interfaces |
| `"minimal"` | Subtle text-only with hover effects | Content-focused designs |

```{r}
# Modern theme
modern_page <- create_page("Modern", data = gss, type = "bar", tabset_theme = "modern") %>%
  add_viz(x_var = "degree", title = "Education", tabgroup = "A") %>%
  add_viz(x_var = "race", title = "Race", tabgroup = "B")

print(modern_page)
```

> **Note:** Tab themes are fully rendered in the generated dashboard. Use `generate_dashboard(render = TRUE)` to see the complete styling.

### Custom Colors

Beyond the built-in themes, you can fully customize tab colors to match your brand or create unique visual designs. Use `tabset_colors` to define a custom color scheme.

The `tabset_colors` parameter accepts a named list with the following color options:

| Parameter | Description | Default |
|-----------|-------------|---------|
| `active_bg` | Background color of the selected tab | Theme-dependent |
| `active_text` | Text color of the selected tab | Theme-dependent |
| `inactive_bg` | Background color of unselected tabs | Transparent |
| `inactive_text` | Text color of unselected tabs | Gray |
| `hover_bg` | Background color when hovering | Light gray |

All colors can be specified as hex codes (e.g., `"#3498DB"`), RGB values (e.g., `"rgb(52, 152, 219)"`), or named colors (e.g., `"steelblue"`).

```{r}
# Blue theme
blue_tabs <- create_page(
  "Blue Theme",
  data = gss,
  type = "bar",
  tabset_theme = "pills",
  tabset_colors = list(
    active_bg = "#3498DB",      # Active tab background
    active_text = "#FFFFFF",    # Active tab text
    inactive_bg = "#ECF0F1",    # Inactive tab background
    inactive_text = "#7F8C8D",  # Inactive tab text
    hover_bg = "#BDC3C7"        # Hover background
  )
) %>%
  add_viz(x_var = "degree", title = "Education", tabgroup = "demo") %>%
  add_viz(x_var = "happy", title = "Happiness", tabgroup = "attitudes")

print(blue_tabs)
```

> **Note:** Custom tab colors (like `tabset_colors`) are only visible in the generated dashboard, not in `preview()`.

### Example: Corporate Theme

Match your organization's brand colors for a cohesive, professional look. Start with your primary brand color for `active_bg`, then derive the other colors from it (lighter versions for `inactive_bg` and `hover_bg`):

```{r}
# Corporate red theme
corporate <- create_page(
  "Corporate",
  data = gss,
  type = "bar",
  tabset_theme = "modern",
  tabset_colors = list(
    active_bg = "#C0392B",      # Brand red
    active_text = "#FFFFFF",
    inactive_bg = "#FADBD8",    # Light red
    inactive_text = "#922B21",
    hover_bg = "#E6B0AA"
  )
) %>%
  add_viz(x_var = "degree", title = "Education", tabgroup = "Q1") %>%
  add_viz(x_var = "race", title = "Demographics", tabgroup = "Q2") %>%
  add_viz(x_var = "happy", title = "Satisfaction", tabgroup = "Q3")

print(corporate)
```

### Example: Dark Theme

For dashboards with dark backgrounds, use high-contrast colors to ensure readability. The `pills` theme works particularly well with dark designs because the rounded buttons create clear visual boundaries:

```{r}
# Dark theme
dark_tabs <- create_page(
  "Dark Theme",
  data = gss,
  type = "bar",
  tabset_theme = "pills",
  tabset_colors = list(
    active_bg = "#2ECC71",      # Bright green accent
    active_text = "#1A1A1A",
    inactive_bg = "#2C3E50",    # Dark background
    inactive_text = "#95A5A6",  # Muted text
    hover_bg = "#34495E"
  )
) %>%
  add_viz(x_var = "degree", title = "Education", tabgroup = "Data") %>%
  add_viz(x_var = "happy", title = "Results", tabgroup = "Analysis")

print(dark_tabs)
```

> **Note:** Tab styling (custom colors, themes) is fully visible only in the generated dashboard. The `preview()` function shows a simplified version without custom tab colors.

## ⚡ Lazy Loading

> **Warning:** Lazy loading is currently **experimental** and may not work reliably in all browsers or configurations. Use with caution in production dashboards.

Lazy loading is a performance optimization technique that defers rendering charts and tab content until they're actually needed. Instead of loading everything when the page opens, content loads as the user scrolls to it or clicks on a tab. This can significantly improve initial page load times for dashboards with many visualizations.

### When to Use Lazy Loading

Consider lazy loading if your dashboard has:

- **Many visualizations** (20+) that slow down initial page load
- **Multiple tabs** where users typically only view a few
- **Heavy charts** like maps or complex scatter plots

### Enable Lazy Loading

| Parameter | Description | Default |
|-----------|-------------|---------|
| `lazy_load_charts` | Load charts only when scrolled into view | `FALSE` |
| `lazy_load_margin` | Distance from viewport to start loading (CSS units) | `"200px"` |
| `lazy_load_tabs` | Load tab content only when tab is clicked | `FALSE` |

```{r, eval=FALSE}
create_page(
  "Large Analysis",
  data = data,
  lazy_load_charts = TRUE,     # Load charts as user scrolls
  lazy_load_margin = "300px",  # Start loading 300px before visible
  lazy_load_tabs = TRUE        # Load tab content when clicked
)
```

### When to Use

### Loading Overlays

Loading overlays provide visual feedback while content renders. They display a spinner or animation that disappears once the page is ready, creating a polished user experience.

> **See it in action:** Check out the [Loading Overlay Demo](../live-demos/overlay/index.html) to experience loading overlays - reload to see the effect.

| Parameter | Description | Options |
|-----------|-------------|---------|
| `overlay` | Enable loading overlay | `TRUE` / `FALSE` |
| `overlay_theme` | Visual style of the overlay | `"light"`, `"dark"`, `"glass"`, `"accent"` |
| `overlay_text` | Custom message to display | Any string |
| `overlay_duration` | Minimum display time (milliseconds) | e.g., `1500` |

```{r, eval=FALSE}
create_page(
  "Analysis",
  data = large_dataset,
  overlay = TRUE,
  overlay_theme = "glass",      # Frosted glass effect
  overlay_text = "Loading analysis...",
  overlay_duration = 1500       # Show for at least 1.5 seconds
)
```

## 🏷️ Powered by dashboardr Branding

Add a subtle "Powered by dashboardr" badge to your dashboard footer. This is entirely optional but helps spread the word about dashboardr!

```{r, eval=FALSE}
dashboard <- create_dashboard("my_project", "My Dashboard") %>%
  add_pages(home, analysis, about) %>%
  add_powered_by_dashboardr()
```

### Style Options

Choose a style that fits your dashboard's aesthetic:

| Style | Description |
|-------|-------------|
| `"default"` | Subtle text with the dashboardr logo |
| `"minimal"` | Just text, no logo - most unobtrusive |
| `"badge"` | Rounded background badge - more visible |

```{r, eval=FALSE}
# Default - subtle text with logo
dashboard %>% add_powered_by_dashboardr(style = "default")

# Minimal - just text, no logo
dashboard %>% add_powered_by_dashboardr(style = "minimal")

# Badge - rounded background badge
dashboard %>% add_powered_by_dashboardr(style = "badge")
```

### Size Options

Control how prominent the branding appears:

```{r, eval=FALSE}
# Small (default) - unobtrusive
dashboard %>% add_powered_by_dashboardr(size = "small")

# Medium - more visible
dashboard %>% add_powered_by_dashboardr(size = "medium")

# Large - prominent
dashboard %>% add_powered_by_dashboardr(size = "large")
```

### Combining with Custom Footer

The branding automatically positions to the right side of the footer, leaving room for your own text on the left:

```{r, eval=FALSE}
create_dashboard(
  "my_project",
  title = "My Dashboard",
  page_footer = "© 2025 My Organization"
) %>%
  add_powered_by_dashboardr()
# Result: Your text on left, dashboardr badge on right
```

## Related Vignettes

- `vignette("getting-started")` - Quick overview
- `vignette("content-collections")` - Content collections deep dive
- `vignette("pages")` - Pages deep dive
- `vignette("dashboards")` - Dashboard creation
