quarto-dev / quarto-dev/quarto-r

Rendering R package vignette with centralized CSS

Open
#284 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
161
Forks
29
Avg merge
3h 18m
Merged PRs (30d)
1

Description

Hi Christophe, @cderv
Thank you for all your work on the quarto-r package and beyond.
I was wondering if there is a way to use CSS styling files dynamically rather than statically to reduce duplication.
This would be especially useful on the Bioconductor Build System where it has access to the appropriate BiocStyle files.
Essentially, we would like to use a "standardized" styling file:

---
title: "Example R Package"
author:
- name: Marcel Ramos
date: last-modified
format:
  html:
    toc: true
    toc-location: left
    number-sections: true
    embed-resources: true
    mainfont: "Atkinson Hyperlegible"
    link-external-newwindow: true
    css: "`r system.file('resources', 'html', 'biocstyle.css', package = 'BiocStyle')`"
vignette: >
  %\VignetteIndexEntry{Example Overview}
  %\VignetteEngine{quarto::format}
  %\VignetteEncoding{UTF-8}
---

Thank you!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the R package vignette example in the issue and investigate how quarto-r handles the CSS value in the HTML format configuration. Determine whether a dynamically evaluated system.file path can be supported for centralized BiocStyle files, and document the supported outcome or limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, r
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.