Introduction | Other options for faking data | What this package does, and does not do | Examples | Fake business transactional data | Steps for creating realistic looking business transactional data | Protected health information | Plumber api | Conclusion

Contributing | Package API | Install | high level function | locale support | generate a dataset | Data types, localized | person name | phone number | job | Data types, universal | currency | credit cards | Missing data | character strings | numeric data | logicals | Messy data

Communication | Definitions | Example | R6 | Inheritance | Locale specific inheritance | Adding new providers or locales | Adding a new locale step by step | Code work: | Documentation work: | Github work: | Adding a new provider, step by step | Guidelines for providers and locales | Where should I add logic or data? | Prior work and related

Overview | 1. Adding a badge

Badges or shields | Use cases | Scenario 0: add a few loose badges | Scenario 1: starting a package with minimal badges | Scenario 2: adding dynamic badges to your readme | Scenario 3: you already have some badges, but you want to add other ones (cran, rdocumentation, travis, etc) | scenario 4: you want to add certain badges, essentially a list of badges that you want, regardless of what is already there (so it should ignore badges, ignore if there is a travis file) | scenario 5: You don't want a RMarkdown file, but a markdown file.

Authentication | Temporary adding acountname and password to your session | Permanently adding username and password to your r session | Getting travel advise | More details about the returned dataframe. | Stationlist | Departures | Disruptions and maintenance | Current disruptions (=unscheduled disruptions + current engineering work) | Scheduled engineering work(=scheduled engineering work) | Current disruptions for a specific station (=unscheduled disruptions + current engineering work)