Relative data, output and static_folder paths resolve against the configuration file. Building
never launches or deploys an app. The configuration is deliberately limited to
data mapping, scientific scale/direction, an optional declared primary model,
metadata, presentation options, and optional study details (schema version 2).
study_info is either the path to a CSV of study details or a lookup object,
{"cache": "study-metadata.csv", "abstracts": "open_licence", "openalex": true},
which runs fetch_study_metadata() on the mapped url column and writes its result
to the cache CSV. Only the cache is required. The lookup is the only network access
during a build; DOIs already found in the cache are not queried again. The generated
app never queries external services.
Arguments
- config
Path to JSON, or a named list with the same schema.
- overwrite
Replace generated files in a nonempty output folder, as in
generate_shiny(). Unrelated files are retained. Checked before any lookup.
Value
Invisibly, the static site directory when static_folder is supplied; otherwise the generated app directory.
Details
Set the optional static_folder string to generate a static shinylive site
in one step, using the same semantics as generate_shiny(). The output
folder retains the editable app. With overwrite = TRUE, the existing static
site folder is deleted entirely and rewritten, including unrelated files.
Keep hand edits in the editable app folder and use export_static() after
editing; regenerating the app replaces edits to its generated files.