What changes | A fresh app | Adding a page | Wiring it up | Adapting an existing golem app | What stays golem

Load package | Use "dev/dev_history.R" | Fill your DESCRIPTION file | Change default parameters | Use the configuration file | Ignore some of the dependencies automatically detected | Add extra Suggests dependencies | Move detected dependencies from Imports to Suggests | A package was not detected by att_amend_desc | I have a Rmarkdown file / Quarto file in my "inst/" directory | I have an R script in my "inst/" directory | Example on a fake package | Propose content for "Remotes" field | Create a file for package installation | Other possibilities

Coming from a single page app | Navigation is a link | What every page shares | Where state goes | What a navigation costs | Several visitors at once | When not to reach for brochure | Where to go next

The order things run in | Logging every request | Answering before Shiny | Rejecting a request | Changing the response | Page level or app level | Pages that answer on another method

A page | An app | Something on every page | How a url finds its page | When no page matches | Reading the parameters | Redirections | Middleware | Behind a reverse proxy | What's next

The routing | Everything else the response carries | Which server a session runs | What a page computes | In a browser

Setting a cookie | Reading it back | Removing it | A session across pages

Does this concern you? | Why a prefix is a problem here | The fix | On Posit Connect | Reading the symptoms | Writing links that survive | Test it deployed | What happens under the hood

Book | Cheatsheet | Agent skills | Videos and talks | Examples apps

Why bootstrict | A first app | Conventions (minimum deviation from Shiny) | The map of the package | How bootstrict differs from Shiny | Overlays live in the UI — they are not built from the server | Server helpers take id first and session last | Two kinds of inputs | bs_button() is an action button only when given an id | Run the bundled apps

Pages | Containers | The grid: rows and columns | bs_row() | bs_col() | Responsive spans | Gutters, alignment and order | Stacks

The motivating workflow | bootstrict_theme() | The _variables.scss sheet | Inspecting a sheet with parse_scss_variables() | Colour modes (Bootstrap 5.3) | Set the initial mode on the page | Flip the mode from the server | Following the operating system | Scope a mode to one component | Utilities | The golem hook | Attaching the dependency by hand

The two families | Text-like inputs | Select | Checkboxes, switches, radios and groups | Range and colour (native inputs) | Dates and files | Composing inputs | Input groups | Floating labels | Forms, labels, help and validation | Dates | Toggle buttons | Validation | Putting it together

Buttons | Download buttons | Cards | Alerts | Badges | Accordion (interactive) | Carousel (interactive) | Collapse (interactive) | List group (interactive) | Progress (interactive) | Spinners and placeholders

Nav vs. tabset | Static nav | Interactive tabset | Navbar | A navbar that switches pages | Breadcrumbs | Pagination | Dropdowns

Tables | Images | Figures | Blockquotes | Display typography | Lists | Small helpers

The overlay model: declare in the UI, open by id | Modal | Dynamic content | Opening without a server round trip | Offcanvas (drawer) | Toasts | Tooltips and popovers | Scrollspy | Inside a Shiny module | The pattern, in one place

Initiate the Continuous Integration (CI) / Continuous Deployment (CD) | For a R package or a {golem} app | For a book | How can I find the pkgdown/book associated with my project | Continuous deployment on Posit Connect | CD of a pkgdown | Create the pkgdown | Initiate the deployment of your pkgdown | To be done on your R project | To be done on Gitlab | How can I find the pkgdown associated with my R package on Posit Connect | CD of a golem shiny app | Add an app.R at the root of your package to deploy on RStudio Connect | Initiate the deployment of your app | How can I find the app associated with my {golem} package | CD of a book | Build your book | Initiate the deployment of your book | How can I find the book deployed on Posit Connect ?

Installing | Getting started | Create a package | dev/01_start.R | Fill the DESCRIPTION | Set common Files | Init Tests | Add various tools | Remove current favicon | Add a new one | Try the app

Day to day development with | Launching the app | dev/02_dev.R | Add dependencies | Add modules | Add function files | Add external files | Adding these external resources to your app | Add a data-raw folder | Add tests | Documentation | Vignette | Code coverage | Using {golem} dev functions

About the run_app() function | Deploying Apps with | Posit Products | Docker | Without using | Using {renv} - CASE 1 : you didn't use renv during development process | Using {renv} - CASE 2: you already have a renv.lock file for your project

Using {golem} js functions | golem::invoke_js() | A quick intro to jQuery selectors

Two Ways to Manage Production vs Development Mode | About inst/golem-config.yml | Setting golem-config | Using golem-config | app_config.R | golem_config vs golem_options | Connecting Back to the R Options Approach | The R Options Mechanism | Important: The Two Mechanisms Are Independent | Best Practices | Note for {golem} < 0.2.0 users

Project Hooks | What it is | How it works | Defining your own project_hook | Example | Module templates | Defining your own module_template | JS & CSS & SASS templates | Defining your own template | Turn on the maintenance mode | How to set the maintenance mode | The maintenance page

Contributing to Golem | Note for the contributors | Code style | Actual state of the package | Code of Conduct

audit_check() - check with CRAN settings | check_n_covr() - check plus coverage in one pass | audit_userspace() - no files left after check

TL;DR - the audit script | Why share the check object? | Per-issue cheatsheet | Globals (no visible binding) | Missing roxygen tags | Non-ASCII characters | Undocumented datasets | Old-style inst/CITATION | Unquoted package names in Description | Network / download calls | \dontrun{} blocks in examples | Minimal end-to-end on a fake package | Next step: pre-submission gates

Write instructions to install all dependencies from a "DESCRIPTION" file

Introduction | Getting Started | Setting Up Your API Token | Projects | Creating and Managing Projects | Tasks | Creating Tasks | Managing Tasks | Filtering Tasks | Sections | Managing Sections | Labels | Managing Labels | Comments | Managing Comments | Filters | Managing Custom Filters | Reminders | Managing Reminders | Collaboration | Managing Users and Collaborators | User Information | Invitations | Workspaces | Managing Workspaces | Activity Logs | Templates | Import and Export Templates | Backups | Managing Backups | File Uploads | Managing File Attachments | Complete Workflow Example | API Reference | Session Info

1 - Get the token | Now save your token securly into R (one time per computer) | 2 - Now, let's play ! | Create new project, add tasks and users | Add new project | Add task to this project | Add users to this porject | All in the same time | More specific :

Rename a flat file | Fully deprecate a flat file after inflate

Move from a package developed with fusen to a "classical" package

Can I be lazy in names used? | Can I knit the content of the flat template ? | How to declare packages with library() for the future vignette ? | How to include examples that cannot be run ? | Document your internal datasets in a function chunk as usual | How to ignore some chunks ? | How to create a vignette with different title and Index Entry? | How not to create a vignette? | How to get a pre-filled template for a specific function name ? | How to pre-fill multiple functions in one template | How to inflate multiple flat files ? | How to store multiple functions in a unique R file ? | All functions under one title section | Use same @rdname in function roxygen | Use same @filename in function roxygen | Use chunk param filename = "the_comon_filename" | How to read dataset that I usually put in "tests/testthat/" for my unit tests? | Can I load all functions of the current flat file during development without having to inflate()? | Can I inflate a Quarto qmd file? | Can I use {fusen} with {golem}? | How can I know if R files were created from a flat or not ? | How can I get rid of everything related to 'fusen' in my package ?

Load package | Use "dev/dev_history.R" | Use {attachment} with {bookdown} / {pagedown} / {quarto} dependencies | Propose content for "Remotes" field | Get all packages listed in "namespace" | Get all packages added using pkg::function or library/require | Get all packages called in your Rmd | Get all packages called in your Rmd and show them in this same Rmd

Get a tree of the package structure to help developers | Get the list of functions from a R file

{fusen} registers all files of your package | What is the configuration file? | What about unregistered files? | Deprecate flat files after inflate | Detect all files that are not registered in configuration file | How register_all_to_config() works

Inflate all your flat files at once | Store configuration of each flat file once | Prevent some flat files to be inflated | Wrapper around inflate_all() | Register all other files to help clean your project | Compute the code coverage | Complete the process with your own code style

Creating connections | function-in-function style | Define a custom function with gitlab() and a temporary connection

Set up GitLab connection | Define the project | Create a project called testor.main, owned by the user | Check created branch (depending on GitLab, main branch may still be "master") | Open the URL of the project | Add/modify and commit the README.md | Create a new branch named "for-tests" | Add and commit a CI file (".gitlab-ci.yml") | Use the commit created above and add a follow-up comment | Create a first issue (#1) with a follow-up comment | Delete project

API calls | Writing custom gitlab request functions

Quick Start Example | Central features of 'gitlabr' | Set connection and explore the GitLab instance | parameter style | Using GitLab CI with 'gitlabr'

Daily use of | Add a new set of chunks in the current Rmd | Create a new flat Rmd template | How to maintain a {fusen}? Can I use {fusen} with old-way packages ? | Option 1: Continue with the "flat_template.Rmd" | Option 2: Maintain like a classical package | What about packages already built the old way ? | Let's try to convince package developers with an example | Compare a classical way of building packages with the {fusen} way

Initiate your package and share it on GitHub | What happens behind the scene ?

All steps to create a package with {fusen} from one Rmd file | Fill your package Description | Inflate your package from the flat Rmd template | Create a new package from command line directly, using a pre-defined template | Add a new "flat_template.Rmd" template in "dev/" directory | There can be development actions | Limitations

Parse and split a Rmd / Qmd file, and transform as tibble | Combine a parsed tbl Rmd / Qmd file into a new file

Init a new project with everything in one command

create_r_project(): Create a R project with full content skeleton | Transform project as book with lozen template with create_book_project() | add_kit_project(): Add necessary files for any R project | add_kit_package(): Add files necessary for a package, including | Add files to buildignore : add_build_ignore() | Add files to gitignore : add_git_ignore() | Use a dev history file

Packages | Define the name of the principal branch | Connection to GitLab | Create a new project or use an existing project | Create a new project | Get groups | Create the new project | Use an existing project | Get all information about the project | Clone your project and add the skeleton for your product (package, app, bookdown) | Define local installation and clone | Create the skeleton for your product and initiate the CI/CD | Initiate the CI/CD | Manage git tools (branches, commits, issues, etc.) | Create and manage the forge board and wiki | Visualise the status of your project

Packages | Define the name of the principal branch | Connexion to GitHub | Create a new project or use an existing project | Create a new project | Use an existing project | Manipulate your project and add everything needed | Define local installation and clone | Create R project skeleton | Create weekly | Manage a calendar | Add commit templates | Add issue templates | Add CI log check for Code coverage | Push to server | Start main and create a production branch | Protect branches | No autoclose issue and coverage regex | Create the board | Add missing labels | Create the wiki pages | Add some special issues in the board | Add the first issue for the client | Add the issue that will be shown during the kick-off | Add the todo for the Lead Dev

For a project on Gitlab | Create a weekly for GitLab with gl_create_weekly() | Visualise the nature of the developments for GitLab with visualise_commits() | Visualise the progress of the milestones for GitLab with gl_get_milestones_progress() | For a project on Github

build_pkgdown_with_reports() : build a pkgdown with coverage and test reports

Add labels | Create the board | Add some special issues in the board | Add the first issue for the client | Add the issue that will be shown during the kick-off | Add the todo for the Lead Dev | Create the wiki pages | No autoclose issue and coverage regex | Add commit templates | Add issues templates

Define local installation and clone | Push to server | Create a production branch | Protect branches | No autoclose issue and coverage regex | Add commit templates | Add issues templates

Fake client database | Fake products | Fake website visits | Fake questionnaire on mean of transport / goal | fake transport use

Travis | Direct | Deploy + pkgdown | tic | Highlights | tic.R | tic_travis.yml

Why use covrpage when developing a package? | Why use covrpage on top of say Codecov and Coveralls? | Is covrpage report only for users? | How is covrpage report built? | How to publish covrpage report? | Conclusion

Test Plans | Test Report

Coverage | Unit Tests

Create book repository inside a package | Create empty book | Build the book based on vignettes | Create short book with index and references only | Help user find the userguides

Create the pkgdown | Help user find the site

Build a reference page | Add references to this page

To describe your package and how to install it | Create and update a custom README with installation instructions

Create reproducible environments for your R projects with

Create a reproducible example of a versioned directory | Build book of commits messages | Read list of commits and extract information | Get commits and find pattern | Create a vignette that lists all files with date of modification

Présentation | Recueil des consommations alimentaires | Fréquentiel alimentaire (FPQ) | Recueil des informations complémentaires | Caractéristiques socio-économiques et niveau de vie | Activité physique et sédentarité | Consommation de compléments alimentaires (CA) | Etat de santé et régimes particuliers | Habitudes et pratiques alimentaires | Mesures et relevés lors de la visite à domicile | Mesures anthropométriques | Participation et effectifs | les différentes bases disponibles | description_indiv_decode | habitudes_indiv_decode | habitudes_men_decode | actphys_sedent_decode | occasions | conso_compo_alim

excel_names : dealing with column names and position number

replace_pattern(): Replace all occurencies of a pattern by replacement | is_likert(): Verify levels of a factor vector

Create directories to mount in the Docker | Create the table of correspondance for additional volumes | Launch Docker with other volumes

Create new package | Use {renv} inside Docker and keep installation of packages | {renv} and its different storage directories | Activate cache shared on host | Keep "renv_instructions.Rmd" up-to-date

Connexion with a mysql container | Launch Docker | Connect to database inside the container | Stop your db container | Stop RStudio Docker container and the network

Create new package | Launch Docker

Coverage | Unit Tests

Case 1: package with a passing Travis build/local R CMD check | Case 2: package with a failing Travis build/local R CMD check

Installation of togglr | From CRAN | From Github | Set toggl Api token | Start the tracking system | Stop the tracking system | Get total time passed on the current project | Get all your dashboard | Use Rstudio Addins | Some other useful functions are in this package

fcuk | Installation of fcuk | Launch and use | Stop fcuk | Recurrent use of fcuk | fcuk functions | Feedbacks and questions