├── .gitignore ├── CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE.md ├── README.md ├── _config.yml ├── _data └── glossary.yml ├── _includes ├── footer.html ├── glossary.html ├── head.html ├── header.html └── navbar.html ├── bin └── check.py ├── etc ├── cc-by.svg ├── github.svg ├── site.css └── tango.css ├── favicon.ico └── index.html /.gitignore: -------------------------------------------------------------------------------- 1 | *~ 2 | .DS_Store 3 | .Rhistory 4 | .Rproj.user 5 | .jekyll-cache 6 | .jekyll-metadata 7 | _site 8 | -------------------------------------------------------------------------------- /CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | In the interest of fostering an open and welcoming environment, we as 4 | contributors and maintainers pledge to making participation in our project and 5 | our community a harassment-free experience for everyone, regardless of age, body 6 | size, disability, ethnicity, gender identity and expression, level of 7 | experience, education, socio-economic status, nationality, personal appearance, 8 | race, religion, or sexual identity and orientation. 9 | 10 | ## Our Standards 11 | 12 | Examples of behavior that contributes to creating a positive environment 13 | include: 14 | 15 | * using welcoming and inclusive language, 16 | * being respectful of differing viewpoints and experiences, 17 | * gracefully accepting constructive criticism, 18 | * focusing on what is best for the community, and 19 | * showing empathy towards other community members. 20 | 21 | Examples of unacceptable behavior by participants include: 22 | 23 | * the use of sexualized language or imagery and unwelcome sexual 24 | attention or advances, 25 | * trolling, insulting/derogatory comments, and personal or political 26 | attacks, 27 | * public or private harassment, 28 | * publishing others' private information, such as a physical or 29 | electronic address, without explicit permission, and 30 | * other conduct which could reasonably be considered inappropriate in 31 | a professional setting 32 | 33 | ## Our Responsibilities 34 | 35 | Project maintainers are responsible for clarifying the standards of acceptable 36 | behavior and are expected to take appropriate and fair corrective action in 37 | response to any instances of unacceptable behavior. 38 | 39 | Project maintainers have the right and responsibility to remove, edit, or reject 40 | comments, commits, code, wiki edits, issues, and other contributions that are 41 | not aligned to this Code of Conduct, or to ban temporarily or permanently any 42 | contributor for other behaviors that they deem inappropriate, threatening, 43 | offensive, or harmful. 44 | 45 | ## Scope 46 | 47 | This Code of Conduct applies both within project spaces and in public spaces 48 | when an individual is representing the project or its community. Examples of 49 | representing a project or community include using an official project e-mail 50 | address, posting via an official social media account, or acting as an appointed 51 | representative at an online or offline event. Representation of a project may be 52 | further defined and clarified by project maintainers. 53 | 54 | ## Enforcement 55 | 56 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 57 | reported by [emailing the project team][email]. All complaints will be 58 | reviewed and investigated and will result in a response that is deemed necessary 59 | and appropriate to the circumstances. The project team is obligated to maintain 60 | confidentiality with regard to the reporter of an incident. Further details of 61 | specific enforcement policies may be posted separately. 62 | 63 | Project maintainers who do not follow or enforce the Code of Conduct in good 64 | faith may face temporary or permanent repercussions as determined by other 65 | members of the project's leadership. 66 | 67 | ## Attribution 68 | 69 | This Code of Conduct is adapted from the [Contributor Covenant][covenant] 70 | version 1.4. 71 | 72 | [email]: mailto:greg.wilson@rstudio.com 73 | [covenant]: https://www.contributor-covenant.org 74 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Our goal is to make this glossary available 4 | both as a web page 5 | and as a package in R and Python 6 | so that the following will work: 7 | 8 | ``` 9 | # In R 10 | > library(glossry) 11 | > define('fully qualified name') 12 | 13 | An unambiguous name of the form `package::thing`. 14 | ``` 15 | 16 | ``` 17 | # In Python 18 | >>> from glossary import define 19 | >>> define('singleton') 20 | 21 | A set with only one element, or a class with only one instance. 22 | ``` 23 | 24 | By submitting material, you are agreeing to abide by our [Code of Conduct](CONDUCT.md) 25 | and to make your contribution available under the terms of our [license](LICENSE.md). 26 | All contributors will be acknowledged by name unless they request otherwise. 27 | 28 | ## Structure 29 | 30 | Terms are defined in `_data/glossary.yml` in order to be compatible with [GitHub Pages][ghp]. 31 | The format of this YAML file is explained below. 32 | To add, extend, amend, or correct a definition, please: 33 | 34 | 1. [File an issue][issues] with the term as the title and the suggested change as the issue body, 35 | or 36 | 37 | 2. [Create a pull request][pr] with the term as the title and the suggested change as a modification to `_data/glossary.yml`. 38 | 39 | 3. Please tag all issues and PRs: 40 | - `enhancement` for new material. 41 | - `alteration` for changes to existing material. 42 | - `requested` for a definition you would like but don't feel able to write. 43 | - `question` and `help wanted` for questions and matters requiring assistance respectively. 44 | 45 | 4. Please put `FIXME` in the text where work is needed. 46 | (We are particularly grateful for contributions that fill in existing `FIXME` markers.) 47 | 48 | ## YAML Format 49 | 50 | Each term is currently defined by a block of YAML formatted as follows: 51 | 52 | ``` 53 | - term: some word or phrase (REQUIRED) 54 | slug: unique-hyphenated-lowercase-id (REQUIRED) 55 | en: > 56 | A paragraph of English, usually indented below the 'en' key to allow line 57 | wrapping. (Notice the '>' after the 'en' key, which tells YAML to expect a 58 | paragraph.) This text should use Markdown formatting, and [word](#some-slug) 59 | for embedded cross-references. 60 | es: > 61 | Spanish definition. Use 'de', 'fr', 'jp', etc. for other languages. 62 | acronym: XYZ (OPTIONAL) 63 | see: (OPTIONAL) 64 | - some-other-slug 65 | - and-yet-another-slug 66 | links: (OPTIONAL) 67 | - title: Your First Reference (REQUIRED) 68 | link: http://some/thing (REQUIRED) 69 | ``` 70 | 71 | This format will evolve as we discover new requirements. 72 | 73 | 1. Please add new terms in alphabetical order. 74 | 75 | 2. Please put special strings like "null" in quotation marks 76 | (because [Norway][norway]). 77 | 78 | ## Checking 79 | 80 | Use `bin/check.py _data/glossary.yml` to check the format and consistency of the glossary. 81 | Enhancements to this script are greatly appreciated. 82 | 83 | [ghp]: https://pages.github.com 84 | [issues]: https://github.com/rstudio-education/glossRy/issues 85 | [norway]: https://third-bit.com/2015/06/11/why-we-cant-have-nice-things.html 86 | [pr]: https://github.com/rstudio-education/glossRy/pulls 87 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | # License 2 | 3 | *This is a human-readable summary of (and not a substitute for) the license. 4 | Please see for the full legal text.* 5 | 6 | This work is licensed under the Creative Commons Attribution 4.0 7 | International license (CC-BY-4.0). 8 | 9 | **You are free to:** 10 | 11 | - **Share**---copy and redistribute the material in any medium or 12 | format 13 | 14 | - **Remix**---remix, transform, and build upon the material for any 15 | purpose, even commercially. 16 | 17 | The licensor cannot revoke these freedoms as long as you follow the 18 | license terms. 19 | 20 | **Under the following terms:** 21 | 22 | - **Attribution**---You must give appropriate credit, provide a link 23 | to the license, and indicate if changes were made. You may do so in 24 | any reasonable manner, but not in any way that suggests the licensor 25 | endorses you or your use. 26 | 27 | - **No additional restrictions**---You may not apply legal terms or 28 | technological measures that legally restrict others from doing 29 | anything the license permits. 30 | 31 | **Notices:** 32 | 33 | You do not have to comply with the license for elements of the 34 | material in the public domain or where your use is permitted by an 35 | applicable exception or limitation. 36 | 37 | No warranties are given. The license may not give you all of the 38 | permissions necessary for your intended use. For example, other rights 39 | such as publicity, privacy, or moral rights may limit how you use the 40 | material. 41 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # glossRy 2 | 3 | A small glossary of terms used in R and data science, designed for novices who 4 | are still orienting themselves. Contributions are very welcome; please see the 5 | [contribution guidelines](CONTRIBUTING.md) if you would like to lend and hand, 6 | and note that all contributors must abide by our [Code of Conduct](CONDUCT.md). 7 | 8 | ## Contributors 9 | 10 | - [Therese Anders](https://dornsife.usc.edu/anders) 11 | - [Maria Bekker-Nielsen Dunbar](https://orcid.org/0000-0002-7249-3524) 12 | - [Marly Cormar](http://www.marlycormar.com/) 13 | - [Joyce Cahoon](https://jcahoon.netlify.com/) 14 | - [Daniel Chen](https://chendaniely.github.io) 15 | - [Desirée De Leon](http://desiree.rbind.io/) 16 | - [Dewey Dunnington](https://fishandwhistle.net/) 17 | - [Maya Gans](https://maya.rbind.io/) 18 | - [Leslie Huang](https://leslie-huang.github.io/) 19 | - [Greg Wilson](http://third-bit.com) 20 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | repository: / 2 | kramdown: 3 | toc_levels: "2" 4 | -------------------------------------------------------------------------------- /_data/glossary.yml: -------------------------------------------------------------------------------- 1 | - term: "+1" 2 | slug: plus-one 3 | en: > 4 | An upvote. FIXME 5 | 6 | - term: A/B testing 7 | slug: ab-testing 8 | en: > 9 | FIXME 10 | 11 | - term: Absolute path 12 | slug: absolute-path 13 | en: > 14 | A path that points to the same location in the filesystem regardless of where 15 | it's evaluated. An absolute path is the equivalent of latitude and longitude 16 | in geography. 17 | see: 18 | - relative-path 19 | 20 | - term: Absolute row number 21 | slug: absolute-row-number 22 | en: > 23 | The sequential index of a row in a table, regardless of what sections of the 24 | table is being displayed. 25 | 26 | - term: Aggregation 27 | slug: aggregation 28 | en: > 29 | To combine many values into one, e.g., by summing a set of numbers or 30 | concatenating a set of strings. 31 | 32 | - term: Aggregation function 33 | slug: aggregation-function 34 | en: > 35 | A function that combines many values into one, such as `sum` or `max`. 36 | 37 | - term: Aliasing 38 | slug: aliasing 39 | en: > 40 | To have two or more references to the same thing, such as a data structure 41 | in memory or a file on disk. 42 | 43 | - term: Anchor tag 44 | slug: anchor-tag 45 | en: > 46 | FIXME 47 | 48 | - term: Anonymous function 49 | slug: anonymous-function 50 | en: > 51 | A function that has not been assigned a name. Anonymous functions are usually 52 | quite short, and are usually defined where they are used, e.g., as 53 | callbacks. 54 | 55 | - term: Application Programming Interface 56 | slug: api 57 | acronym: API 58 | en: > 59 | A set of functions and procedures provided by one software library or web service 60 | through which another application can communicate with it. 61 | An API is not the code, the database, or the server: 62 | it's the access point. 63 | 64 | - term: Argument 65 | slug: argument 66 | en: > 67 | A value passed into a function. Some authors use the term as a synonym for 68 | [parameter](#parameter) and some do not; it's all very confusing. 69 | 70 | - term: ASCII 71 | slug: ascii 72 | en: > 73 | A standard way to represent the characters commonly used in the Western 74 | European languages as 7- or 8-bit integers, now superceded by [Unicode](#unicode). 75 | 76 | - term: Attribute 77 | slug: attribute 78 | en: > 79 | A name-value pair associated with an object, used to store metadata about the 80 | object such as an array's dimensions. 81 | 82 | - term: Back end 83 | slug: back-end 84 | en: > 85 | FIXME 86 | 87 | - term: Backward-compatible 88 | slug: backward-compatible 89 | en: > 90 | Software which is able to be used the same way as earlier versions of itself 91 | without problems. 92 | 93 | - term: Base R 94 | slug: base-r 95 | en: > 96 | The basic functions making up the R language. 97 | The base packages can be found in `src/library` and are not updated outside of R; 98 | their version numbers follow R version numbering. 99 | Base packages are installed and loaded with R, 100 | while priority packages are installed with base R but must be loaded prior to use. 101 | see: 102 | - tidyverse 103 | 104 | - term: Binary 105 | slug: binary 106 | en: > 107 | FIXME 108 | 109 | - term: Binding 110 | slug: binding 111 | en: > 112 | FIXME 113 | 114 | - term: Branch 115 | slug: branch 116 | en: > 117 | A snapshot of a version of a Git repository. Multiple branches can capture 118 | multiple versions of the same repository. 119 | see: 120 | - feature-branch 121 | - fork 122 | - master-branch 123 | 124 | - term: Breadcrumbs 125 | slug: breadcrumbs 126 | en: > 127 | A set of supplementary navigational links included in many websites, usually placed at the top of the page. 128 | Breadcrumbs show the users where the current page lies in the website; 129 | the term comes from a fairy tale in which children left a trail of breadcrumbs behind themselves 130 | so that they could find their way home. 131 | 132 | - term: Call stack 133 | slug: call-stack 134 | en: > 135 | A data structure that stores information about the active subroutines 136 | executed. `cst()` is a useful function provided in the `lobstr` package to 137 | visualize a call stack. 138 | 139 | - term: Call to action 140 | slug: call-to-action 141 | en: > 142 | FIXME 143 | 144 | - term: Cascading Style Sheets 145 | slug: css 146 | acronym: CSS 147 | en: > 148 | A way to control the appearance of HTML. CSS is typically used to specify 149 | fonts, colors, and layout. 150 | 151 | - term: Catch (exception) 152 | slug: catch-exception 153 | en: > 154 | To accept responsibility for handling an error or other unexpected event. R 155 | prefers "handling a condition" to "catching an exception". 156 | see: 157 | - condition 158 | - handle-condition 159 | 160 | - term: Character encoding 161 | slug: character-encoding 162 | en: > 163 | A specification of how characters are stored as bytes. The most commonly-used 164 | encoding today is [UTF-8](#utf-8). 165 | 166 | - term: Cherry picking (in Git) 167 | slug: cherry-picking 168 | en: > 169 | FIXME 170 | 171 | - term: Class 172 | slug: class 173 | en: > 174 | FIXME 175 | 176 | - term: Closure 177 | slug: closure 178 | en: > 179 | A set of variables defined in the same [scope](#scope) whose existence has been 180 | preserved after that scope has ended. Closures are one of the trickiest 181 | ideas in programming. 182 | 183 | - term: Code hook 184 | slug: code-hook 185 | en: > 186 | FIXME 187 | 188 | - term: Coercion 189 | slug: coercion 190 | en: > 191 | see [type coercion](#type-coercion). 192 | 193 | - term: Comma-Separated Values 194 | slug: csv 195 | acronym: CSV 196 | en: > 197 | A text format for tabular data in which each record is one row and fields are 198 | separated by commas. There are many minor variations, particularly around 199 | quoting of strings. 200 | 201 | - term: Condition 202 | slug: condition 203 | en: > 204 | An error or other unexpected event that disrupts the normal flow of control. 205 | see: 206 | - handle-condition 207 | 208 | - term: Constant 209 | slug: constant 210 | en: > 211 | FIXME 212 | 213 | - term: Constructor 214 | slug: constructor 215 | en: > 216 | A function that creates an object of a particular class. In the 217 | [S3](#s3) object system, constructors are a convention rather than a 218 | requirement. 219 | 220 | - term: Copy-on-modify 221 | slug: copy-on-modify 222 | en: > 223 | The practice of creating a new copy of aliased data whenever there is an 224 | attempt to modify it so that each reference will believe theirs is the only 225 | one. 226 | see: 227 | - aliasing 228 | 229 | - term: CRAN 230 | slug: cran 231 | en: > 232 | The Comprehensive R Archive Network is a public repository of R packages. 233 | see: 234 | - base-r 235 | - tidyverse 236 | 237 | - term: Creative Commons licenses 238 | slug: cc-license 239 | en: > 240 | A set of licenses that can be applied to published work. 241 | Each license is formed by concatenating one or more of 242 | `-BY` (Attribution): users must cite the original source; 243 | `-SA` (ShareAlike): users must share their own work under a similar license; 244 | `-NC` (NonCommercial): work may not be used for commercial purposes without the creator's permission; 245 | `-ND` (NoDerivatives): no derivative works (e.g., translations) can be created without the creator's permission. 246 | Thus, `CC-BY-NC` means "users must give attribution and cannot use commercially without permission 247 | The term `CC-0` (zero, not letter 'O') is sometimes used to mean "no restrictions", i.e., the work is in the public domain. 248 | 249 | - term: CSS selector 250 | slug: css-selector 251 | en: > 252 | FIXME 253 | see: 254 | - css 255 | 256 | - term: Data frame 257 | slug: data-frame 258 | en: > 259 | A two-dimensional data structure for storing tabular data in memory. 260 | Rows represent [records](#record) and columns represent [variables](variable-data). 261 | see: 262 | - tidy-data 263 | 264 | - term: Diff (in Git) 265 | slug: diff 266 | en: > 267 | FIXME 268 | 269 | - term: Docker 270 | slug: docker 271 | en: > 272 | FIXME. 273 | 274 | - term: Double 275 | slug: double 276 | en: > 277 | Short for "double-precision floating-point number", meaning a 64-bit numeric 278 | value with a fractional part and an exponent. 279 | 280 | - term: Double square brackets 281 | slug: double-square-brackets 282 | en: > 283 | An index enclosed in `[[...]]`, used to return a single value of the 284 | underlying type. 285 | see: 286 | - single-square-brackets 287 | 288 | - term: Dynamic scoping 289 | slug: dynamic-scoping 290 | en: > 291 | FIXME. 292 | see: 293 | - lexical-scoping 294 | 295 | - term: Eager evaluation 296 | slug: eager-evaluation 297 | en: > 298 | FIXME. 299 | see: 300 | - lazy-evaluation 301 | 302 | - term: Empty vector 303 | slug: empty-vector 304 | en: > 305 | A vector that contains no elements. Empty vectors have a type such as logical 306 | or character, and are *not* the same as [null](#null). 307 | 308 | - term: Environment 309 | slug: environment 310 | en: > 311 | A structure that stores a set of variable names and the values they refer to. 312 | 313 | - term: Error handling 314 | slug: error-handling 315 | en: > 316 | What a program does to detect and correct for errors. 317 | Examples include printing a message and 318 | using a default configuration if the user-specified configuration can't be found. 319 | 320 | - term: Escape sequence 321 | slug: escape-sequence 322 | en: > 323 | A sequence of characters used to represent some other character that would 324 | otherwise have a special meaning. For example, the escape sequence `\"` is 325 | used to represent a double-quote character inside a double-quoted string. 326 | 327 | - term: Evaluation 328 | slug: evaluation 329 | en: > 330 | The process of taking an expression such as `1+2*3/4` and turning it 331 | into a single irreducible value. 332 | 333 | - term: Exception 334 | slug: exception 335 | en: > 336 | An object that stores information about an error or other unusual event in a 337 | program. One part of a program will create and [raise](#raise) an exception to 338 | signal that something unexpected has happened; another part will [catch](#catch-exception) 339 | it. 340 | 341 | - term: Falsy 342 | slug: falsy 343 | en: > 344 | A horrible neologism meaning "equivalent to false". 345 | see: 346 | - truthy 347 | 348 | - term: Feature branch 349 | slug: feature-branch 350 | en: > 351 | A branch within a Git repository containing commits dedicated to a specific feature, 352 | e.g., a bug fix or a new function. 353 | This branch can be merged into another branch. 354 | see: 355 | - master-branch 356 | 357 | - term: Field (database) 358 | slug: field 359 | en: > 360 | FIXME 361 | 362 | - term: Filter 363 | slug: filter 364 | en: > 365 | To choose a set of [records](#record) (i.e., rows of a table) based 366 | on the values they contain. 367 | 368 | - term: Fork 369 | slug: fork 370 | en: > 371 | A copy of one person's Git repository that lives in another person's GitHub 372 | account. Changes to the content of a fork can be submitted to the [upstream 373 | repository](#upstream-repository) via a [pull request](#pull-request). 374 | see: 375 | - branch 376 | 377 | - term: Front end 378 | slug: front-end 379 | en: > 380 | FIXME 381 | 382 | - term: Fully-qualified name 383 | slug: fully-qualified-name 384 | en: > 385 | An unambiguous name of the form `package::thing`. 386 | 387 | - term: Functional programming 388 | slug: functional-programming 389 | en: > 390 | A style of programming in which data is transformed through successive 391 | application of functions, rather than by using control structures such as 392 | loops. 393 | see: 394 | - higher-order-function 395 | - object-oriented-programming 396 | 397 | - term: Generic function 398 | slug: generic-function 399 | en: > 400 | A collection of functions with similar purpose, each operating on a different 401 | class of data. 402 | 403 | - term: Git 404 | slug: git 405 | en: > 406 | a version control tool to record and manage changes to a project. 407 | 408 | - term: GitHub 409 | slug: github 410 | en: > 411 | A cloud-based platform built around [Git](#git) that allows you to save versions 412 | of your project online and collaborate with other Git users. 413 | 414 | - term: Global environment 415 | slug: global-environment 416 | en: > 417 | The [environment](#environment) that holds top-level definitions in R, 418 | e.g., those written directly in the interpreter. 419 | 420 | - term: Global installation 421 | slug: global-installation 422 | en: > 423 | Installing a package in a location where it can be accessed by all users and 424 | projects. 425 | see: 426 | - local-installation 427 | 428 | - term: Global variable 429 | slug: global-variable 430 | en: > 431 | A variable defined outside any particular function, which is therefore visible 432 | to all functions. 433 | see: 434 | - local-variable 435 | 436 | - term: GNU Public License 437 | slug: gpl 438 | acronym: GPL 439 | en: > 440 | A license that allows people to re-use software as long as they distribute the 441 | source of their changes. 442 | 443 | - term: Group 444 | slug: group 445 | en: > 446 | To divide data into subsets according to some criteria while leaving records 447 | in a single structure. 448 | 449 | - term: Handle (condition) 450 | slug: handle-condition 451 | en: > 452 | To accept responsibility for handling an error or other 453 | unexpected event. R prefers "handling a condition" to "catching an 454 | exception". 455 | see: 456 | - condition 457 | - exception 458 | 459 | - term: Header row 460 | slug: header-row 461 | en: > 462 | If present, the first row of a CSV file that defines column names (but 463 | tragically, not their data types or units). 464 | see: 465 | - csv 466 | 467 | - term: Heterogeneous 468 | slug: heterogeneous 469 | en: > 470 | Having mixed type. For example, an list can contain a mix of numbers, 471 | character strings, and values of other types. 472 | see: 473 | - homogeneous 474 | 475 | - term: Higher-order function 476 | slug: higher-order-function 477 | en: > 478 | A function that operates on other functions. For example, the higher-order 479 | function `map` executes a given function once on each value in an 480 | [list](#list). Higher-order functions are heavily used in [functional 481 | programming](#functional-programming). 482 | 483 | - term: Homogeneous 484 | slug: homogeneous 485 | en: > 486 | Having a single type. For example, a [vector](#vector) must be homogeneous: its 487 | values must all be numeric, logical, etc. 488 | 489 | - term: Hook 490 | slug: hook 491 | en: > 492 | FIXME 493 | see: 494 | - code-hook 495 | 496 | - term: Instance 497 | slug: instance 498 | en: > 499 | FIXME 500 | 501 | - term: Integrated Development Environment 502 | slug: ide 503 | acronym: IDE 504 | en: > 505 | An application that helps programmers develop software. 506 | IDEs typically have a built-in editor, a console to execute code immediately, 507 | and browsers for exploring data structures in memory and files on disk. 508 | see: 509 | - repl 510 | 511 | - term: Interactive rebase (in Git) 512 | slug: interactive-rebase 513 | en: > 514 | FIXME 515 | 516 | - term: JSON 517 | slug: json 518 | en: > 519 | A way to represent data by combining basic values like numbers and character 520 | strings in lists and name/value structures. The acronym stands for 521 | "JavaScript Object Notation"; unlike better-defined standards like [XML](#xml), 522 | it is unencumbered by a syntax for comments or ways to define a [schema](#schema). 523 | 524 | - term: knitr 525 | slug: knitr 526 | en: > 527 | FIXME. 528 | see: 529 | - r-markdown 530 | 531 | - term: Lazy evaluation 532 | slug: lazy-evaluation 533 | en: > 534 | Delaying evaluation of an expression until the value is actually needed (or at 535 | least until after the point where it is first encountered). 536 | 537 | - term: Lexical scoping 538 | slug: lexical-scoping 539 | en: > 540 | FIXME. 541 | see: 542 | - dynamic-scoping 543 | 544 | - term: LGTM (Looks Good to Me) 545 | slug: lgtm 546 | en: > 547 | FIXME 548 | 549 | - term: Library 550 | slug: library 551 | en: > 552 | FIXME 553 | see: 554 | - package 555 | 556 | - term: List 557 | slug: list 558 | en: > 559 | A [vector](#vector) that can contain values of many different types. 560 | 561 | - term: Literate programming 562 | slug: literate-programming 563 | en: > 564 | A programming paradigm that mixes prose and code. 565 | see: 566 | - r-markdown 567 | 568 | - term: Local installation 569 | slug: local-installation 570 | en: > 571 | Placing a package inside a particular project so that it is only accessible 572 | within that project. 573 | see: 574 | - global-installation 575 | 576 | - term: Local variable 577 | slug: local-variable 578 | en: > 579 | A variable defined inside a function which is only visible within that 580 | function. 581 | see: 582 | - closure 583 | - global-variable 584 | 585 | - term: Logical indexing 586 | slug: logical-indexing 587 | en: > 588 | To index a vector or other structure with a vector of Booleans, keeping only 589 | the values that correspond to true values. Also referred to as [masking](#masking). 590 | 591 | - term: Make 592 | slug: make 593 | en: > 594 | FIXME 595 | see: 596 | - makefile 597 | 598 | - term: Makefile 599 | slug: makefile 600 | en: > 601 | FIXME 602 | 603 | - term: Markdown 604 | slug: markdown 605 | en: > 606 | A markup language with a simple syntax intended as a replacement for HTML. 607 | Markdown is often used for README files, 608 | and is the basis for [R markdown](R-markdown). 609 | 610 | - term: Masking 611 | slug: masking 612 | en: > 613 | FIXME 614 | see: 615 | - logical-indexing 616 | 617 | - term: Master branch 618 | slug: master-branch 619 | en: > 620 | A dedicated, permanent, central branch which should contain a "ready product". 621 | As a new feature is developed on a separate branch to avoid breaking the main code, 622 | it can be merged into the master branch. 623 | see: 624 | - feature-branch 625 | 626 | - term: Merge (data) 627 | slug: merge-data 628 | en: > 629 | FIXME 630 | 631 | - term: Merge (Git) 632 | slug: merge-git 633 | en: > 634 | Merging branches in Git incorporates development histories of two branches in one. 635 | If changes are made to similar parts of the branches on both branches 636 | a commit will occur and this must be resolved before the merge will be completed. 637 | 638 | - term: Method 639 | slug: method 640 | en: > 641 | An implementation of a [generic function](#generic-function) that handles objects of a specific class. 642 | 643 | - term: MIT License 644 | slug: mit-License 645 | en: > 646 | A license that allows people to re-use software with no restrictions. 647 | 648 | - term: Module 649 | slug: module 650 | en: > 651 | FIXME 652 | see: 653 | - package 654 | 655 | - term: Mutation 656 | slug: mutation 657 | en: > 658 | Changing data in place, such as modifying an element of an array or adding a 659 | record to a database. 660 | 661 | - term: NA 662 | slug: na 663 | en: > 664 | A special value used to represent data that is not available. 665 | see: 666 | - "null" 667 | 668 | - term: Name collision 669 | slug: name-collision 670 | en: > 671 | The ambiguity that arises when two or more things in a program that have the 672 | same name are active at the same time. 673 | see: 674 | - call-stack 675 | - fully-qualified-name 676 | - namespace 677 | 678 | - term: Namespace 679 | slug: namespace 680 | en: > 681 | FIXME 682 | 683 | - term: Native app 684 | slug: native-app 685 | en: > 686 | FIXME 687 | 688 | - term: Negative selection 689 | slug: negative-selection 690 | en: > 691 | To specify the elements of a vector or other data structure that aren't 692 | desired by negating their indices. 693 | 694 | - term: Non-standard evaluation 695 | slug: non-standard-evaluation 696 | acronym: NSE 697 | en: > 698 | FIXME 699 | see: 700 | - lazy-evaluation 701 | 702 | - term: NoSQL database 703 | slug: nosql-database 704 | en: > 705 | Any database that doesn't use the relational model. The awkward name comes 706 | from the fact that such databases don't use [SQL](#sql) as a query language. 707 | see: 708 | - relational-database 709 | 710 | - term: "Null" 711 | slug: "null" 712 | en: > 713 | A special value used to represent a missing object. Null is not the same as 714 | NA, and neither is the same as an [empty vector](#empty-vector). 715 | 716 | - term: Object-oriented programming 717 | slug: object-oriented-programming 718 | acronym: OOP 719 | en: > 720 | FIXME 721 | 722 | - term: Observation 723 | slug: observation 724 | en: > 725 | FIXME 726 | 727 | - term: Package 728 | slug: package 729 | en: > 730 | A collection of code, data, and documentation that can be distributed and 731 | re-used. Also referred to in some languages as a [library](#library) or 732 | [module](#module). 733 | 734 | - term: Package manager 735 | slug: package-manager 736 | en: > 737 | A program that does its best to keep track of the bits and bobs of software 738 | installed on a computer and their dependencies on one another. 739 | 740 | - term: Parameter 741 | slug: parameter 742 | en: > 743 | A variable whose value is passed into a function when the function is 744 | called. Some writers distinguish parameters (the variables) from 745 | [arguments](#argument) (the values passed in), but others use the terms in the 746 | opposite sense. It's all very confusing. 747 | 748 | - term: Parse 749 | slug: parse 750 | en: > 751 | To translate the text of a program or web page into a data structure in memory 752 | that the program can then manipulate. 753 | 754 | - term: Peanuts 755 | slug: peanuts 756 | en: > 757 | An American comic strip by Charles M. Schulz which has inspired the names of R versions. 758 | 759 | - term: Permalink 760 | slug: permalink 761 | en: > 762 | Short for "permanent link", the full URL that you see and use for a post, page, or a site's content. 763 | An example could be `https://www.mysite.com/category/post-name`. 764 | 765 | - term: Pipe operator 766 | slug: pipe-operator 767 | en: > 768 | The `%>%` used to make the output of one function the input of the next. 769 | 770 | - term: Prefix operator 771 | slug: prefix-operator 772 | en: > 773 | FIXME 774 | 775 | - term: Production code 776 | slug: production-code 777 | en: > 778 | Software that is delivered to an end user. The term is used to distinguish 779 | such code from test code, deployment infrastructure, and everything else 780 | that programmers write along the way. 781 | 782 | - term: Pseudo-random number 783 | slug: pseudo-random-number 784 | en: > 785 | A value generated in a repeatable way that resemble the true randomness of 786 | the universe well enough to fool merely mortal observers. 787 | 788 | - term: Pseudo-random number generator 789 | slug: prng 790 | acronym: PRNG 791 | en: > 792 | A function that can generate [pseudo-random numbers](#pseudo-random-number). 793 | see: 794 | - seed 795 | 796 | - term: Pull indexing 797 | slug: pull-indexing 798 | en: > 799 | Vectorized indexing in which the value at location `i` in the index vector 800 | specifies which element of the source vector is being pulled into that 801 | location in the result vector, i.e., `result[i] = source[index[i]]`. 802 | see: 803 | - push-indexing 804 | 805 | - term: Pull request 806 | slug: pull-request 807 | en: > 808 | The request to merge a new feature or correction created on a user's fork of a 809 | [Git](#git) repository into the [upstream repository](#upstream-repository). The 810 | developer will be notified of the change, review it, make or suggest 811 | changes, and potentially merge it. 812 | see: 813 | - fork 814 | 815 | - term: Push indexing 816 | slug: push-indexing 817 | en: > 818 | Vectorized indexing in which the value at location `i` in the index vector 819 | specifies an element of the result vector that gets the corresponding 820 | element of the source vector, i.e., `result[index[i]] = source[i]`. Push 821 | indexing can easily produce gaps and collisions. 822 | see: 823 | - pull-indexing 824 | 825 | - term: Quosure 826 | slug: quosure 827 | en: > 828 | A data structure containing an unevaluated expression and its environment. 829 | 830 | - term: Quoting function 831 | slug: quoting-function 832 | en: > 833 | A function that is passed expressions rather than the values of those 834 | expressions. 835 | 836 | - term: R Consortium 837 | slug: r-consortium 838 | en: > 839 | FIXME 840 | 841 | - term: R Foundation 842 | slug: r-foundation 843 | en: > 844 | A non-profit founded by the R development core team providing support for R. 845 | It is a member of the [R Consortium](#r-consortium). 846 | 847 | - term: R hub 848 | slug: r-hub 849 | en: > 850 | A free platform available to check a `R` package on several different 851 | platforms in preparation for the CRAN submission process. 852 | 853 | - term: R Markdown 854 | slug: r-markdown 855 | en: > 856 | A dialect of [Markdown](#markdown) that allows authors to mix prose 857 | and code (usually written in R) in a single document. Cf. 858 | [literate programming](#literate-programming). 859 | 860 | - term: Raise 861 | slug: raise 862 | en: > 863 | To signal that something unexpected or unusual has happened in a program by 864 | creating an [exception](#exception) and handing it to the error-handling system, which 865 | then tries to find a point in the program that will [catch](#catch-exception) it. 866 | 867 | - term: Reactive programming 868 | slug: reactive-programming 869 | en: > 870 | A style of programming in which actions are triggered by external events. 871 | 872 | - term: Reactive variable 873 | slug: reactive-variable 874 | en: > 875 | A variable whose value is automatically updated when some other value or 876 | values change. Reactive variables are used extensively in [Shiny](#shiny). 877 | 878 | - term: Read-eval-print loop 879 | slug: repl 880 | acronym: repl 881 | en: > 882 | An interactive program that reads a command typed in by a user, 883 | executes it, prints the result, and then waits patiently for the next 884 | command. REPLs are often used to explore new ideas or for debugging. 885 | see: 886 | - ide 887 | 888 | - term: Rebase 889 | slug: rebase 890 | en: > 891 | FIXME 892 | 893 | - term: Record (database) 894 | slug: record 895 | en: > 896 | FIXME 897 | 898 | - term: Recycle 899 | slug: recycle 900 | en: > 901 | To re-use values from a shorter vector in order to generate a sequence of 902 | the same length as a longer one. 903 | 904 | - term: Refactor (code) 905 | slug: refactor-code 906 | en: > 907 | FIXME 908 | 909 | - term: Refactor (R function) 910 | slug: refactor-r 911 | en: > 912 | FIXME 913 | 914 | - term: Regular expression 915 | slug: regular-expression 916 | en: > 917 | A pattern for matching text, written as text itself. Regular expressions are 918 | sometimes called "regexp", "regex", or "RE", and are as powerful as they are 919 | cryptic. 920 | 921 | - term: Relational database 922 | slug: relational-database 923 | en: > 924 | A database that organizes information into tables, each of which has a fixed 925 | set of named fields (shown as columns) and a variable number of records 926 | (shown as rows). 927 | see: 928 | - sql 929 | - table 930 | 931 | - term: Relative path 932 | slug: relative-path 933 | en: > 934 | A path whose destination is interpreted relative to some other location, such 935 | as the current directory. A relative path is the equivalent of giving 936 | directions using terms like "straight" and "left". 937 | see: 938 | - absolute-path 939 | 940 | - term: Relative row number 941 | slug: relative-row-number 942 | en: > 943 | The index of a row in a displayed portion of a table, which may or may not be 944 | the same as the [absolute row number](#absolute-row-number) within the table. 945 | 946 | - term: Repository 947 | slug: repository 948 | en: > 949 | A place where a [version control system](#version-control-system) stores 950 | the files that make up a project and the metadata that describes their history. 951 | see: 952 | - git 953 | - github 954 | 955 | - term: Reprex 956 | slug: reprex 957 | en: > 958 | A reproducible example. When asking questions about coding problems online 959 | or filing issues on GitHub, you should always include a reprex so others can 960 | reproduce your problem and help. The 961 | [reprex](https://github.com/tidyverse/reprex) package can help! 962 | 963 | - term: Root directory 964 | slug: root-directory 965 | en: > 966 | The directory that contains everything else, directly or indirectly. The root 967 | directory is written `/` (a bare forward slash). 968 | 969 | - term: S 970 | slug: s-language 971 | en: > 972 | A language originally developed in Bell Labs for data analysis, statistical 973 | modeling, and graphics. R is a dialect of S. 974 | 975 | - term: S3 976 | slug: s3 977 | en: > 978 | A framework for object-oriented programming in R. 979 | 980 | - term: S4 981 | slug: s4 982 | en: > 983 | A framework for object-oriented programming in R. 984 | 985 | - term: Scalar 986 | slug: scalar 987 | en: > 988 | A single value of a particular type, such as 1 or "a". Scalars don't really 989 | exist in R; values that appear to be scalars are actually vectors of unit 990 | length. 991 | 992 | - term: Schema 993 | slug: schema 994 | en: > 995 | A specification of the format of a dataset, including the name, format, and 996 | content of each [table](#table). 997 | 998 | - term: Scope 999 | slug: scope 1000 | en: > 1001 | The portion of a program within which a definition can be seen and used. Cf. 1002 | [closure](#closure), [global variable](#global-variable), and [local variable](#local-variable). 1003 | 1004 | - term: Script 1005 | slug: script 1006 | en: > 1007 | Originally, a program written in a language too usable for "real" programmers 1008 | to take seriously; the term is now synonymous with program. 1009 | 1010 | - term: Seed 1011 | slug: seed 1012 | en: > 1013 | A value used to initialize a [pseudo-random number generator](#prng). 1014 | 1015 | - term: Select 1016 | slug: select 1017 | en: > 1018 | To choose entire columns from a table by name or location. 1019 | 1020 | - term: Shiny 1021 | slug: shiny 1022 | en: > 1023 | FIXME 1024 | 1025 | - term: Signal (a condition) 1026 | slug: signal 1027 | en: > 1028 | A way of indicating that something has gone wrong in a program, or that some 1029 | other unexpected event has occurred. R prefers "signalling a condition" to 1030 | "raising an exception". 1031 | 1032 | - term: Single square brackets 1033 | slug: single-square-brackets 1034 | en: > 1035 | An index enclosed in `[...]`, used to select a structure from another 1036 | structure. 1037 | see: 1038 | - double-square-brackets 1039 | 1040 | - term: Singleton 1041 | slug: singleton 1042 | en: > 1043 | A set with only one element, or a [class](#class) with only one [instance](#instance). 1044 | 1045 | - term: Slug 1046 | slug: slug 1047 | en: > 1048 | An abbreviated portion of a page's URL that uniquely identifies it. 1049 | In the example `https://www.mysite.com/category/post-name`, the slug is `post-name`. 1050 | 1051 | - term: SQL 1052 | slug: sql 1053 | en: > 1054 | The language used for writing queries for a [relational database](#relational-database). The term 1055 | was originally an acronym for Structured Query Language. 1056 | 1057 | - term: Squash (in Git) 1058 | slug: squash 1059 | en: > 1060 | FIXME 1061 | 1062 | - term: Stack frame 1063 | slug: stack-frame 1064 | en: > 1065 | FIXME 1066 | 1067 | - term: Stash (in Git) 1068 | slug: stash 1069 | en: > 1070 | FIXME 1071 | 1072 | - term: String 1073 | slug: string 1074 | en: > 1075 | A block of text in a program. The term is short for "character string". 1076 | 1077 | - term: String interpolation 1078 | slug: string-interpolation 1079 | en: > 1080 | The process of inserting text corresponding to specified values into a string, 1081 | usually to make output human-readable. 1082 | 1083 | - term: Table 1084 | slug: table 1085 | en: > 1086 | A set of records in a [relational database](#relational-database) or 1087 | observations in a [data frame](#data-frame). Tables are usually displayed 1088 | as rows (each of which represents one [record](#record) or 1089 | [observation](#observation)) and columns (each of which represents a 1090 | [field](#field) or [variable](#variable-data)). 1091 | 1092 | - term: Tibble 1093 | slug: tibble 1094 | en: > 1095 | A modern replacement for R's data frame, which stores tabular data in columns 1096 | and rows, defined and used in the [tidyverse](#tidyverse). 1097 | 1098 | - term: Tidy data 1099 | slug: tidy-data 1100 | en: > 1101 | Tabular data that satisfies [three 1102 | conditions](https://vita.had.co.nz/papers/tidy-data.pdf) that facilitate 1103 | initial cleaning, and later exploration and analysis: (1) each variable 1104 | forms a column, (2) each observation forms a row, and (3) each type of 1105 | observation unit forms a table. 1106 | see: 1107 | - table 1108 | 1109 | - term: tidymodels 1110 | slug: tidymodels 1111 | en: > 1112 | A collection of R packages for modeling and statistical analysis designed with 1113 | a [shared philosophy](https://tidymodels.github.io/model-implementation-principles/index.html). 1114 | 1115 | - term: Tidyverse 1116 | slug: tidyverse 1117 | en: > 1118 | A collection of R packages for operating on tabular data in consistent ways. 1119 | 1120 | - term: Truthy 1121 | slug: truthy 1122 | en: > 1123 | A truly Orwellian neologism meaning "not equivalent to false". Cf. 1124 | [falsy](#falsy), but only if you are able to set aside your respect for the 1125 | English language. 1126 | 1127 | - term: Type coercion 1128 | slug: type-coercion 1129 | en: > 1130 | FIXME 1131 | 1132 | - term: Unicode 1133 | slug: unicode 1134 | en: > 1135 | A standard that defines numeric codes for many thousands of characters and 1136 | symbols. Unicode does not define how those numbers are stored; that is done 1137 | by standards like [UTF-8](#utf-8). 1138 | 1139 | - term: Unit test 1140 | slug: unit-test 1141 | en: > 1142 | A test that exercises one property or expected behavior of a system. 1143 | FIXME: provide example. 1144 | 1145 | - term: Upstream repository 1146 | slug: upstream-repository 1147 | en: > 1148 | FIXME 1149 | 1150 | - term: UTF-8 1151 | slug: utf-8 1152 | en: > 1153 | A way to store the numeric codes representing Unicode characters in memory 1154 | that is [backward-compatible](#backward-compatible) with the older [ASCII](#ascii) standard. 1155 | 1156 | - term: Variable (data) 1157 | slug: variable-data 1158 | en: > 1159 | FIXME 1160 | 1161 | - term: Variable (program) 1162 | slug: variable-program 1163 | en: > 1164 | A name in a program that has some data associated with it. A variable's value 1165 | can be changed after definition. 1166 | see: 1167 | - constant 1168 | 1169 | - term: Variable arguments 1170 | slug: variable-arguments 1171 | en: > 1172 | In a function, the ability to take any number of arguments. R uses `...` to 1173 | capture the "extra" arguments. 1174 | 1175 | - term: Vector 1176 | slug: vector 1177 | en: > 1178 | A sequence of values, usually of [homogeneous](#homogeneous) type. Vectors are the 1179 | fundamental data structure in R; a [scalar](#scalar) is just a vector with exactly 1180 | one element. 1181 | 1182 | - term: Vectorize 1183 | slug: vectorize 1184 | en: > 1185 | To write code so that operations are performed on entire vectors, rather than 1186 | element-by-element within loops. 1187 | 1188 | - term: Version control system 1189 | slug: version-control-system 1190 | en: > 1191 | A system for managing changes made to software during its development. 1192 | see: 1193 | - git 1194 | 1195 | - term: Vignette 1196 | slug: vignette 1197 | en: > 1198 | A long-form guide used to provide details of a package beyond the README.md or 1199 | function documentation. 1200 | 1201 | - term: Whitespace 1202 | slug: whitespace 1203 | en: > 1204 | The space, newline, carriage return, and horizontal and vertical tab 1205 | characters that take up space but don't create a visible mark. The name 1206 | comes from their appearance on a printed page in the era of typewriters. 1207 | 1208 | - term: XML 1209 | slug: xml 1210 | en: > 1211 | A set of rules for defining HTML-like tags and using them to format documents 1212 | (typically data). XML achieved license plate popularity in the early 2000s, 1213 | but its complexity led many programmers to adopt [JSON](#json) instead. 1214 | 1215 | - term: YAML 1216 | slug: yaml 1217 | en: > 1218 | FIXME 1219 | -------------------------------------------------------------------------------- /_includes/footer.html: -------------------------------------------------------------------------------- 1 | 13 | -------------------------------------------------------------------------------- /_includes/glossary.html: -------------------------------------------------------------------------------- 1 |
2 | {% assign heading = nil %} 3 | {% for entry in site.data.glossary %} 4 | {% assign current = entry.term | slice: 0 | upcase %} 5 | {% if current != heading %} 6 | {% if heading != nil %}{% endif %} 7 | {% assign heading = current %} 8 |

{{current}}

9 |
10 | {% endif %} 11 |
{{entry.term | markdownify | replace: '

', '' | replace: '

', ''}}
12 |
{{entry.en | markdownify | replace: '

', '' | replace: '

', ''}}
13 | {% endfor %} 14 |
15 |
16 | -------------------------------------------------------------------------------- /_includes/head.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | -------------------------------------------------------------------------------- /_includes/header.html: -------------------------------------------------------------------------------- 1 |
2 |

Glossary

3 |
4 | -------------------------------------------------------------------------------- /_includes/navbar.html: -------------------------------------------------------------------------------- 1 | 12 | -------------------------------------------------------------------------------- /bin/check.py: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env python 2 | 3 | import sys 4 | import re 5 | import yaml 6 | 7 | 8 | USAGE = 'check.py [/path/to/glossary.yml]' 9 | REQUIRED = ['slug', 'term'] 10 | LANGUAGES = { 11 | 'en': 'English' 12 | } 13 | CROSSREF = re.compile(r'\[.+?\]\(#(.+?)\)') 14 | 15 | 16 | def main(text): 17 | '''Check contents of glossary.''' 18 | 19 | content = yaml.load(text, Loader=yaml.Loader) 20 | known = set([entry['slug'] for entry in content]) 21 | 22 | # All entries have required keys. 23 | for entry in content: 24 | for req in REQUIRED: 25 | check(req in entry, 26 | f'Require {req} in entry {entry}') 27 | 28 | # Entries are alphabetical. 29 | actual = [entry['term'].lower() for entry in content] 30 | sorted = actual[:] 31 | sorted.sort() 32 | for [a, s] in zip(actual, sorted): 33 | check(a == s, 34 | f'Terms {a} and {s} are not in alphabetical order') 35 | 36 | # Cross-references. 37 | for entry in content: 38 | slug = entry['slug'] 39 | 40 | # External cross-references resolve. 41 | if 'see' in entry: 42 | for key in entry['see']: 43 | check(key in known, 44 | f'Bad cross-reference {key} in {slug}') 45 | 46 | # Internal cross-references resolve. 47 | for lang in LANGUAGES: 48 | if lang in entry: 49 | for crossref in CROSSREF.findall(entry[lang]): 50 | check(crossref in known, 51 | f'Bad cross-reference {crossref} in {LANGUAGES[lang]} body of {slug}') 52 | 53 | 54 | def check(test, msg): 55 | '''Report violation of a single check.''' 56 | if not test: 57 | print(msg) 58 | 59 | 60 | def fail(msg): 61 | '''Fail due to internal error.''' 62 | print(msg, file=sys.stderr) 63 | sys.exit(1) 64 | 65 | 66 | # Main driver. 67 | if __name__ == '__main__': 68 | if len(sys.argv) == 1: 69 | main(sys.stdin.read()) 70 | elif len(sys.argv) == 2: 71 | with open(sys.argv[1], 'r') as reader: 72 | main(reader.read()) 73 | else: 74 | fail(USAGE) 75 | -------------------------------------------------------------------------------- /etc/cc-by.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 19 | 21 | 43 | 45 | 46 | 48 | image/svg+xml 49 | 51 | 52 | 53 | 54 | 58 | 64 | 69 | 70 | 73 | 74 | 77 | 81 | 82 | 86 | 87 | 88 | 89 | 92 | 93 | 102 | 103 | 106 | 109 | 110 | 111 | 112 | 113 | 114 | 116 | 126 | 127 | 129 | 132 | 133 | 142 | 143 | 144 | 145 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | -------------------------------------------------------------------------------- /etc/github.svg: -------------------------------------------------------------------------------- 1 | GitHub icon 2 | -------------------------------------------------------------------------------- /etc/site.css: -------------------------------------------------------------------------------- 1 | body { 2 | font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; 3 | padding: 1em; 4 | width: 60em; 5 | line-height: 120%; 6 | } 7 | 8 | header { 9 | margin-left: 2em; 10 | } 11 | 12 | nav { 13 | height: 100%; 14 | width: 2em; 15 | padding-left: 1em; 16 | position: fixed; 17 | z-index: 1; 18 | top: 0; 19 | left: 0; 20 | overflow-x: hidden; 21 | padding-top: 1em; 22 | } 23 | 24 | main { 25 | margin-left: 2em; 26 | padding: 0px 10px; 27 | } 28 | 29 | footer { 30 | border-top: solid 1px #000000; 31 | padding-bottom: 2px; 32 | text-align: center; 33 | background-color: #f8f8f8; 34 | } 35 | 36 | img.footer { 37 | vertical-align: middle; 38 | height: 2em; 39 | padding: 0.25em; 40 | } 41 | 42 | code { 43 | font-family: Monaco,Courier New; 44 | font-size: 80%; 45 | } 46 | 47 | dt { 48 | font-weight: bold; 49 | } 50 | 51 | dd { 52 | margin-left: 1em; 53 | margin-bottom: 0.25em; 54 | } 55 | -------------------------------------------------------------------------------- /etc/tango.css: -------------------------------------------------------------------------------- 1 | .highlight .hll { background-color: #ffffcc } 2 | .highlight { background: #f8f8f8; } 3 | .highlight .c { color: #8f5902; font-style: italic } /* Comment */ 4 | .highlight .err { color: #a40000; border: 1px solid #ef2929 } /* Error */ 5 | .highlight .g { color: #000000 } /* Generic */ 6 | .highlight .k { color: #204a87; font-weight: bold } /* Keyword */ 7 | .highlight .l { color: #000000 } /* Literal */ 8 | .highlight .n { color: #000000 } /* Name */ 9 | .highlight .o { color: #ce5c00; font-weight: bold } /* Operator */ 10 | .highlight .x { color: #000000 } /* Other */ 11 | .highlight .p { color: #000000; font-weight: bold } /* Punctuation */ 12 | .highlight .ch { color: #8f5902; font-style: italic } /* Comment.Hashbang */ 13 | .highlight .cm { color: #8f5902; font-style: italic } /* Comment.Multiline */ 14 | .highlight .cp { color: #8f5902; font-style: italic } /* Comment.Preproc */ 15 | .highlight .cpf { color: #8f5902; font-style: italic } /* Comment.PreprocFile */ 16 | .highlight .c1 { color: #8f5902; font-style: italic } /* Comment.Single */ 17 | .highlight .cs { color: #8f5902; font-style: italic } /* Comment.Special */ 18 | .highlight .gd { color: #a40000 } /* Generic.Deleted */ 19 | .highlight .ge { color: #000000; font-style: italic } /* Generic.Emph */ 20 | .highlight .gr { color: #ef2929 } /* Generic.Error */ 21 | .highlight .gh { color: #000080; font-weight: bold } /* Generic.Heading */ 22 | .highlight .gi { color: #00A000 } /* Generic.Inserted */ 23 | .highlight .go { color: #000000; font-style: italic } /* Generic.Output */ 24 | .highlight .gp { color: #8f5902 } /* Generic.Prompt */ 25 | .highlight .gs { color: #000000; font-weight: bold } /* Generic.Strong */ 26 | .highlight .gu { color: #800080; font-weight: bold } /* Generic.Subheading */ 27 | .highlight .gt { color: #a40000; font-weight: bold } /* Generic.Traceback */ 28 | .highlight .kc { color: #204a87; font-weight: bold } /* Keyword.Constant */ 29 | .highlight .kd { color: #204a87; font-weight: bold } /* Keyword.Declaration */ 30 | .highlight .kn { color: #204a87; font-weight: bold } /* Keyword.Namespace */ 31 | .highlight .kp { color: #204a87; font-weight: bold } /* Keyword.Pseudo */ 32 | .highlight .kr { color: #204a87; font-weight: bold } /* Keyword.Reserved */ 33 | .highlight .kt { color: #204a87; font-weight: bold } /* Keyword.Type */ 34 | .highlight .ld { color: #000000 } /* Literal.Date */ 35 | .highlight .m { color: #0000cf; font-weight: bold } /* Literal.Number */ 36 | .highlight .s { color: #4e9a06 } /* Literal.String */ 37 | .highlight .na { color: #c4a000 } /* Name.Attribute */ 38 | .highlight .nb { color: #204a87 } /* Name.Builtin */ 39 | .highlight .nc { color: #000000 } /* Name.Class */ 40 | .highlight .no { color: #000000 } /* Name.Constant */ 41 | .highlight .nd { color: #5c35cc; font-weight: bold } /* Name.Decorator */ 42 | .highlight .ni { color: #ce5c00 } /* Name.Entity */ 43 | .highlight .ne { color: #cc0000; font-weight: bold } /* Name.Exception */ 44 | .highlight .nf { color: #000000 } /* Name.Function */ 45 | .highlight .nl { color: #f57900 } /* Name.Label */ 46 | .highlight .nn { color: #000000 } /* Name.Namespace */ 47 | .highlight .nx { color: #000000 } /* Name.Other */ 48 | .highlight .py { color: #000000 } /* Name.Property */ 49 | .highlight .nt { color: #204a87; font-weight: bold } /* Name.Tag */ 50 | .highlight .nv { color: #000000 } /* Name.Variable */ 51 | .highlight .ow { color: #204a87; font-weight: bold } /* Operator.Word */ 52 | .highlight .w { color: #f8f8f8; text-decoration: underline } /* Text.Whitespace */ 53 | .highlight .mb { color: #0000cf; font-weight: bold } /* Literal.Number.Bin */ 54 | .highlight .mf { color: #0000cf; font-weight: bold } /* Literal.Number.Float */ 55 | .highlight .mh { color: #0000cf; font-weight: bold } /* Literal.Number.Hex */ 56 | .highlight .mi { color: #0000cf; font-weight: bold } /* Literal.Number.Integer */ 57 | .highlight .mo { color: #0000cf; font-weight: bold } /* Literal.Number.Oct */ 58 | .highlight .sa { color: #4e9a06 } /* Literal.String.Affix */ 59 | .highlight .sb { color: #4e9a06 } /* Literal.String.Backtick */ 60 | .highlight .sc { color: #4e9a06 } /* Literal.String.Char */ 61 | .highlight .dl { color: #4e9a06 } /* Literal.String.Delimiter */ 62 | .highlight .sd { color: #8f5902; font-style: italic } /* Literal.String.Doc */ 63 | .highlight .s2 { color: #4e9a06 } /* Literal.String.Double */ 64 | .highlight .se { color: #4e9a06 } /* Literal.String.Escape */ 65 | .highlight .sh { color: #4e9a06 } /* Literal.String.Heredoc */ 66 | .highlight .si { color: #4e9a06 } /* Literal.String.Interpol */ 67 | .highlight .sx { color: #4e9a06 } /* Literal.String.Other */ 68 | .highlight .sr { color: #4e9a06 } /* Literal.String.Regex */ 69 | .highlight .s1 { color: #4e9a06 } /* Literal.String.Single */ 70 | .highlight .ss { color: #4e9a06 } /* Literal.String.Symbol */ 71 | .highlight .bp { color: #3465a4 } /* Name.Builtin.Pseudo */ 72 | .highlight .fm { color: #000000 } /* Name.Function.Magic */ 73 | .highlight .vc { color: #000000 } /* Name.Variable.Class */ 74 | .highlight .vg { color: #000000 } /* Name.Variable.Global */ 75 | .highlight .vi { color: #000000 } /* Name.Variable.Instance */ 76 | .highlight .vm { color: #000000 } /* Name.Variable.Magic */ 77 | .highlight .il { color: #0000cf; font-weight: bold } /* Literal.Number.Integer.Long */ 78 | -------------------------------------------------------------------------------- /favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rstudio-education/glossRy/bcd8aa8aa6a6de3a68c4a5bffc19d020043d379d/favicon.ico -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | --- 2 | --- 3 | 4 | {% include head.html %} 5 | 6 | {% include navbar.html %} 7 | {% include header.html %} 8 | {% include glossary.html %} 9 | {% include footer.html %} 10 | 11 | 12 | --------------------------------------------------------------------------------