By default, pkgdown will generate an index that simply lists all the functions in alphabetical order. To override this, provide a reference section in your _pkgdown.yml as described below.

build_reference(pkg = ".", lazy = TRUE, examples = TRUE,
run_dont_run = FALSE, mathjax = TRUE, seed = 1014,
path = "docs/reference", depth = 1L)

build_reference_index(pkg = ".", path = "docs/reference", depth = 1L)

## Arguments

pkg Path to source package. If TRUE, only rebuild pages where the .Rd is more recent than the .html. This makes it much easier to rapidly protoype. It is set to FALSE by build_site. Run examples? Run examples that are surrounded in \dontrun? Use mathjax to render math symbols? Seed used to initialize so that random examples are reproducible. Output path. Relative paths are taken relative to the pkg directory. Depth of path relative to root of documentation. Used to adjust relative links in the navbar.

## YAML config

To tweak the index page, you need a section called reference which provides a list of sections containing, a title, list of contents, and optional description.

For example, the following code breaks up the functions in pkgdown into two groups:

reference:
- title: Render components
desc:  Build each component of the site.
contents:
- starts_with("build_")
- init_site
- title: Templates
contents:
- render_page


Note that contents can contain either a list of function names, or if the functions in a section share a common prefix or suffix, you can use starts_with("prefix") and ends_with("suffix") to select them all. For more complex naming schemes you can use an aribrary regular expression with matches("regexp"). You can also use a leading - to exclude matches from a section. By default, these functions that match multiple topics will exclude topics with keyword "internal". To include, use (e.g.) starts_with("build_", internal = TRUE).

Alternatively, you can selected topics that contain specified concepts with has_concept("blah"). Concepts are not currently well-supported by roxygen2, but may be useful if you write Rd files by hand.

pkgdown will check that all non-internal topics are included on this page, and will generate a warning if you have missed any.

## Icons

You can optionally supply an icon for each help topic. To do so, you'll need a top-level icons directory. This should contain .png files that are either 40x40 (for regular display) or 80x80 (if you want retina display). Icons are matched to topics by aliases.

## Examples

# This example illustrates some important output types
# The following output should be wrapped over multiple lines
a <- 1:100
a#>   [1]   1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16  17  18
#>  [19]  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36
#>  [37]  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  52  53  54
#>  [55]  55  56  57  58  59  60  61  62  63  64  65  66  67  68  69  70  71  72
#>  [73]  73  74  75  76  77  78  79  80  81  82  83  84  85  86  87  88  89  90
#>  [91]  91  92  93  94  95  96  97  98  99 100
cat("This some text!\n")#> This some text!message("This is a message!")#> This is a message!warning("This is a warning!")#> Warning: This is a warning!
## Not run: ------------------------------------
# stop("This is an error!", call. = FALSE)
## ---------------------------------------------

# This code won't generally be run by CRAN. But it
# will be run by testthat.
b <- 10
a + b#>   [1]  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28
#>  [19]  29  30  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46
#>  [37]  47  48  49  50  51  52  53  54  55  56  57  58  59  60  61  62  63  64
#>  [55]  65  66  67  68  69  70  71  72  73  74  75  76  77  78  79  80  81  82
#>  [73]  83  84  85  86  87  88  89  90  91  92  93  94  95  96  97  98  99 100
#>  [91] 101 102 103 104 105 106 107 108 109 110