Hao Zhu | 1fc48a6 | 2017-03-01 14:07:54 -0500 | [diff] [blame] | 1 | --- |
| 2 | title: "Create Awesome HTML Table with knitr::kable and kableExtra" |
| 3 | author: "Hao Zhu" |
| 4 | date: "`r Sys.Date()`" |
| 5 | output: |
| 6 | html_document: |
| 7 | toc: true |
| 8 | toc_depth: 2 |
| 9 | toc_float: true |
| 10 | vignette: > |
| 11 | %\VignetteIndexEntry{Create Awesome HTML Table with knitr::kable and kableExtra} |
| 12 | %\VignetteEngine{knitr::rmarkdown} |
| 13 | %\VignetteEncoding{UTF-8} |
| 14 | --- |
| 15 | |
Hao Zhu | 63e0986 | 2017-03-01 16:30:34 -0500 | [diff] [blame] | 16 | > ⚠ For LaTeX tables, please see the [package site](http://haozhu233.github.io/kableExtra/) for more information. |
| 17 | |
Hao Zhu | 1fc48a6 | 2017-03-01 14:07:54 -0500 | [diff] [blame] | 18 | # Overview |
| 19 | The goal of `kableExtra` is to help you build common complex tables and manipulate table styles. It imports the pipe `%>%` symbol from `magrittr` and verbalize all the functions, so basically you can add "layers" to a kable output in a way that is similar with `ggplot2` and `plotly`. |
| 20 | |
| 21 | # Installation |
| 22 | Some LaTeX features in `kableExtra`, such as striped line, requires rmarkdown 1.4.0+, which is not yet on CRAN. It is highly recommended to install the dev version of rmarkdown before you try this package. If you only use this package for HTML table, it doesn't matter what version of rmarkdown you are using. |
| 23 | ```r |
| 24 | # install.packages("devtools") |
| 25 | devtools::install_github("rstudio/rmarkdown") |
| 26 | |
| 27 | # For dev version |
| 28 | devtools::install_github("haozhu233/kableExtra") |
| 29 | ``` |
| 30 | # Getting Started |
| 31 | Here we are using the first few columns and rows from dataset `mtcars` |
| 32 | ```{r} |
| 33 | library(knitr) |
| 34 | library(kableExtra) |
| 35 | dt <- mtcars[1:5, 1:6] |
| 36 | ``` |
| 37 | |
| 38 | When 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.* |
| 39 | |
| 40 | ```{r} |
| 41 | options(knitr.table.format = "html") |
| 42 | ## If you don't define format here, you'll need put `format = "html"` in every kable function. |
| 43 | ``` |
| 44 | |
| 45 | ## Basic HTML Table |
| 46 | Basic HTML output of `kable` looks very crude. To the end, it's just a plain HTML table without any love from css. |
| 47 | ```{r} |
| 48 | kable(dt) |
| 49 | ``` |
| 50 | |
| 51 | ## Apply Bootstrap |
| 52 | When used on a HTML table, `kable_styling()` will automatically apply twitter bootstrap theme to the table. Now it should looks the same as the original pandoc output (the one when you don't specify `format` in `kable()`) but this time, you are controlling it. |
| 53 | ```{r} |
| 54 | kable(dt) %>% |
| 55 | kable_styling() |
| 56 | ``` |
| 57 | |
| 58 | # Table Styles |
| 59 | `kable_styling` offers server other ways to customize the look of a HTML table. |
| 60 | |
| 61 | ## Bootstrap Options |
| 62 | If you are not familiar with twitter bootstrap, you probably have already known its predefined classes, including `striped`, `bordered`, `hover`, `condensed` and `responsive`. If you are not familiar, no worries, you can take a look at their [documentation site](http://getbootstrap.com/css/#tables) to get a sense of how they look like. All of these options are available here. |
| 63 | |
| 64 | For example, to add striped lines (alternative row colors) to your table and you want to highlight the hovered row, you can simply type: |
| 65 | ```{r} |
| 66 | kable(dt) %>% |
| 67 | kable_styling(bootstrap_options = c("striped", "hover")) |
| 68 | ``` |
| 69 | |
| 70 | The option `condensed` can also be handy in many cases when you don't want your table to be too large. It has slightly shorter row height. |
| 71 | ```{r} |
| 72 | kable(dt) %>% |
| 73 | kable_styling(bootstrap_options = c("striped", "hover", "condensed")) |
| 74 | ``` |
| 75 | |
| 76 | Tables with option `responsive` looks the same with others on a large screen. However, on a small screen like phone, they are horizontally scrollable. Please resize your window to see the result. |
| 77 | ```{r} |
| 78 | kable(dt) %>% |
| 79 | kable_styling(bootstrap_options = c("striped", "hover", "condensed", "responsive")) |
| 80 | ``` |
| 81 | |
| 82 | ## Full Width or Not? |
| 83 | By 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 as long as you specified. ) |
| 84 | ```{r} |
| 85 | kable(dt) %>% |
| 86 | kable_styling(bootstrap_options = "striped", full_width = F) |
| 87 | ``` |
| 88 | |
| 89 | ## Position |
| 90 | Table 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 |
| 91 | ```{r} |
| 92 | kable(dt) %>% |
| 93 | kable_styling(bootstrap_options = "striped", full_width = F, position = "left") |
| 94 | ``` |
| 95 | |
| 96 | Becides these three common options, you can also wrap text around the table using the `float-left` or `float-right` options. |
| 97 | ```{r} |
| 98 | kable(dt) %>% |
| 99 | kable_styling(bootstrap_options = "striped", full_width = F, position = "float_right") |
| 100 | ``` |
| 101 | Lorem 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. |
| 102 | |
| 103 | ## Font Size |
| 104 | If 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. |
| 105 | ```{r} |
| 106 | kable(dt) %>% |
| 107 | kable_styling(bootstrap_options = "striped", font_size = 7) |
| 108 | ``` |
| 109 | |
| 110 | # Add Extra Header Rows |
| 111 | Tables 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)). |
| 112 | ```{r} |
| 113 | kable(dt) %>% |
| 114 | kable_styling("striped") %>% |
| 115 | add_header_above(c(" " = 1, "Group 1" = 2, "Group 2" = 2, "Group 3" = 2)) |
| 116 | ``` |
| 117 | |
| 118 | In fact, if you want to add another row of header on top, please feel free to do so. |
| 119 | ```{r} |
| 120 | kable(dt) %>% |
| 121 | kable_styling(c("striped", "bordered")) %>% |
| 122 | add_header_above(c(" ", "Group 1" = 2, "Group 2" = 2, "Group 3" = 2)) %>% |
| 123 | add_header_above(c(" ", "Group 4" = 4, "Group 5" = 2)) %>% |
| 124 | add_header_above(c(" ", "Group 6" = 6)) |
| 125 | ``` |
| 126 | |
| 127 | # Add footnote |
| 128 | ## Notation System |
| 129 | You 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. |
| 130 | |
| 131 | ### Alphabet |
| 132 | ```{r} |
| 133 | kable(dt) %>% |
| 134 | kable_styling("striped") %>% |
| 135 | add_footnote(c("Footnote 1", "Have a good day."), notation = "alphabet") |
| 136 | ``` |
| 137 | |
| 138 | ### Number |
| 139 | ```{r} |
| 140 | kable(dt) %>% |
| 141 | kable_styling("striped") %>% |
| 142 | add_footnote(c("Footnote 1", "Have a good day."), notation = "number") |
| 143 | ``` |
| 144 | |
| 145 | ### Symbol |
| 146 | ```{r} |
| 147 | kable(dt) %>% |
| 148 | kable_styling("striped") %>% |
| 149 | add_footnote(c("Footnote 1", "Footnote 2", "Footnote 3"), notation = "symbol") |
| 150 | ``` |
| 151 | |
| 152 | ## In-table markers |
| 153 | By design, `add_footnote()` will transform any `[note]` to in-table footnote markers. |
| 154 | ```{r} |
| 155 | kable(dt, caption = "Demo Table[note]") %>% |
| 156 | kable_styling("striped") %>% |
| 157 | add_header_above(c(" ", "Group 1[note]" = 3, "Group 2[note]" = 3)) %>% |
| 158 | add_footnote(c("This table is from mtcars", |
| 159 | "Group 1 contains mpg, cyl and disp", |
| 160 | "Group 2 contains hp, drat and wt"), |
| 161 | notation = "symbol") |
| 162 | ``` |