blob: 2ca1bb0adc6ac1b640ff48b6a0f51baca282bb75 [file] [log] [blame]
Hao Zhu3fb64062017-06-09 10:57:43 -04001---
2title: "kableExtra in other rmarkdown HTML themes"
3author: "Hao Zhu"
4date: "`r Sys.Date()`"
5output:
6 prettydoc::html_pretty:
7 theme: cayman
8---
9
10# Intro
11If you plan to use `kableExtra` in a non-bootstrap HTML theme, feel free to do so. The only part that will be impacted is the `bootstrap_options` in `kable_styling` (that's why it's named in this way). This document shows the look of tables in [`prettydoc`](https://github.com/yixuan/prettydoc) (by [yixuan](https://github.com/yixuan)).
12
13# Getting Started
14Here we are using the first few columns and rows from dataset `mtcars`
15```{r}
16library(knitr)
17library(kableExtra)
18dt <- mtcars[1:5, 1:6]
19```
20
21When you are using `kable()`, if you don't specify `format`, by default it will generate a markdown table and let pandoc handle the conversion from markdown to HTML/PDF. This is the most favorable approach to render most simple tables as it is format independent. If you switch from HTML to pdf, you basically don't need to change anything in your code. However, markdown doesn't support complex table. For example, if you want to have a double-row header table, markdown just cannot provide you the functionality you need. As a result, when you have such a need, you should **define `format` in `kable()`** as either "html" or "latex". *You can also define a global option at the beginning using `options(knitr.table.format = "html")` so you don't repeat the step everytime.*
22
23```{r}
24options(knitr.table.format = "html")
25## If you don't define format here, you'll need put `format = "html"` in every kable function.
26```
27
28## Basic HTML Table
29Basic HTML output of `kable` looks not bad in `prettydoc` because themes in `prettydoc` have already changed the theme of `table`.
30```{r}
31kable(dt)
32```
33
34## Full Width or Not?
35By default, a bootstrap table takes 100% of the width. It is supposed to use together with its grid system to scale the table properly. However, when you are writing a rmarkdown document, you probably don't want to write your own css/or grid. For some small tables with only few columns, a page wide table looks awful. To make it easier, you can specify whether you want the table to have `full_width` or not in `kable_styling`. By default, `full_width` is set to be `TRUE` for HTML tables (note that for LaTeX, the default is `FALSE` since I don't want to change the "common" looks unless you specified it.)
36```{r}
37kable(dt) %>%
38 kable_styling(full_width = F)
39```
40
41## Position
42Table Position only matters when the table doesn't have `full_width`. You can choose to align the table to `center`, `left` or `right` side of the page
43```{r}
44kable(dt) %>%
45 kable_styling(full_width = F, position = "left")
46```
47
48Becides these three common options, you can also wrap text around the table using the `float-left` or `float-right` options.
49```{r}
50kable(dt) %>%
51 kable_styling(full_width = F, position = "float_right")
52```
53Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras sit amet mauris in ex ultricies elementum vel rutrum dolor. Phasellus tempor convallis dui, in hendrerit mauris placerat scelerisque. Maecenas a accumsan enim, a maximus velit. Pellentesque in risus eget est faucibus convallis nec at nulla. Phasellus nec lacinia justo. Morbi fermentum, orci id varius accumsan, nibh neque porttitor ipsum, consectetur luctus risus arcu ac ex. Aenean a luctus augue. Suspendisse et auctor nisl. Suspendisse cursus ultrices quam non vulputate. Phasellus et pharetra neque, vel feugiat erat. Sed feugiat elit at mauris commodo consequat. Sed congue lectus id mattis hendrerit. Mauris turpis nisl, congue eget velit sed, imperdiet convallis magna. Nam accumsan urna risus, non feugiat odio vehicula eget.
54
55## Font Size
56If one of your tables is huge and you want to use a smaller font size for that specific table, you can use the `font_size` option.
57```{r}
58kable(dt) %>%
59 kable_styling(font_size = 7)
60```
61
62# Add Extra Header Rows
63Tables with multi-row headers can be very useful to demonstrate grouped data. To do that, you can pipe your kable object into `add_header_above()`. The header variable is supposed to be a named character with the names as new column names and values as column span. For your convenience, if column span equals to 1, you can ignore the `=1` part so the function below can be written as `add_header_above(c(" ", "Group 1" = 2, "Group 2" = 2, "Group 3" = 2)).
64```{r}
65kable(dt) %>%
66 kable_styling("striped") %>%
67 add_header_above(c(" " = 1, "Group 1" = 2, "Group 2" = 2, "Group 3" = 2))
68```
69
70In fact, if you want to add another row of header on top, please feel free to do so.
71```{r}
72kable(dt) %>%
73 kable_styling(c("striped", "bordered")) %>%
74 add_header_above(c(" ", "Group 1" = 2, "Group 2" = 2, "Group 3" = 2)) %>%
75 add_header_above(c(" ", "Group 4" = 4, "Group 5" = 2)) %>%
76 add_header_above(c(" ", "Group 6" = 6))
77```
78
79# Add footnote
80## Notation System
81You can also use `add_footnote()` function from this package. You will need to supply a character vector with each element as one footnote. You may select from `number`, `alphabet` and `symbol` for different types of notations. Example are listed below.
82
83### Alphabet
84```{r}
85kable(dt) %>%
86 kable_styling("striped") %>%
87 add_footnote(c("Footnote 1", "Have a good day."), notation = "alphabet")
88```
89
90### Number
91```{r}
92kable(dt) %>%
93 kable_styling("striped") %>%
94 add_footnote(c("Footnote 1", "Have a good day."), notation = "number")
95```
96
97### Symbol
98```{r}
99kable(dt) %>%
100 kable_styling("striped") %>%
101 add_footnote(c("Footnote 1", "Footnote 2", "Footnote 3"), notation = "symbol")
102```
103
104## In-table markers
105By design, `add_footnote()` will transform any `[note]` to in-table footnote markers.
106```{r}
107kable(dt, caption = "Demo Table[note]") %>%
108 kable_styling("striped") %>%
109 add_header_above(c(" ", "Group 1[note]" = 3, "Group 2[note]" = 3)) %>%
110 add_footnote(c("This table is from mtcars",
111 "Group 1 contains mpg, cyl and disp",
112 "Group 2 contains hp, drat and wt"),
113 notation = "symbol")
114```
115
116***
117
118The following features are introduced in `kableExtra` 0.2.0.
119
120# Group Rows
Hao Zhu72917f92019-03-15 18:41:42 -0400121Sometimes we want a few rows of the table being grouped together. They might be items under the same topic (e.g., animals in one species) or just different data groups for a categorical variable (e.g., age < 40, age > 40). With the new function `pack_rows()` in `kableExtra`, this kind of task can be completed in one line. Please see the example below. Note that when you count for the start/end rows of the group, you don't need to count for the header rows nor other group label rows. You only need to think about the row numbers in the "original R dataframe".
Hao Zhu3fb64062017-06-09 10:57:43 -0400122```{r}
123kable(mtcars[1:10, 1:6], caption = "Group Rows") %>%
124 kable_styling("striped", full_width = F) %>%
Hao Zhu72917f92019-03-15 18:41:42 -0400125 pack_rows("Group 1", 4, 7) %>%
126 pack_rows("Group 2", 8, 10)
Hao Zhu3fb64062017-06-09 10:57:43 -0400127```
128
129For advanced users, you can even define your own css for the group labeling.
130```{r}
131kable(dt) %>%
132 kable_styling("striped", full_width = F) %>%
Hao Zhu72917f92019-03-15 18:41:42 -0400133 pack_rows("Group 1", 3, 5, label_row_css = "background-color: #666; color: #fff;")
Hao Zhu3fb64062017-06-09 10:57:43 -0400134```
135
136# Add indentation
Hao Zhu72917f92019-03-15 18:41:42 -0400137Unlike `pack_rows()`, which will insert a labeling row, sometimes we want to list a few sub groups under a total one. In that case, `add_indent()` is probably more apporiate.
Hao Zhu3fb64062017-06-09 10:57:43 -0400138For advanced users, you can even define your own css for the group labeling.
139```{r}
140kable(dt) %>%
141 kable_styling("striped", full_width = F) %>%
142 add_indent(c(1, 3, 5))
143```
144
145***
146
147The following feature is introduced in `kableExtra` 0.2.1.
148
149# Column Style Specification
150When you have a table with lots of explanatory texts, you may want to specified the column width for different column, since the auto adjust in HTML may not work in its best way while basic LaTeX table is really bad at handling text wrapping. Also, sometimes, you may want to highlight a column (e.g. a "Total" column) by making it bold. In these scenario, you can use `column_spec()`. You can find an example below.
151```{r}
152text_tbl <- data.frame(
153 Items = c("Item 1", "Item 2", "Item 3"),
154 Features = c(
155 "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin vehicula tempor ex. Morbi malesuada sagittis turpis, at venenatis nisl luctus a. ",
156 "In eu urna at magna luctus rhoncus quis in nisl. Fusce in velit varius, posuere risus et, cursus augue. Duis eleifend aliquam ante, a aliquet ex tincidunt in. ",
157 "Vivamus venenatis egestas eros ut tempus. Vivamus id est nisi. Aliquam molestie erat et sollicitudin venenatis. In ac lacus at velit scelerisque mattis. "
158 )
159)
160
161kable(text_tbl) %>%
162 kable_styling(full_width = F) %>%
163 column_spec(1, bold = T) %>%
164 column_spec(2, width = "30em")
165```