Ideas that have not worked:

• adding these "landscape mode" braces around results chunk in skeleton, and/or specific R chunk in 08_tables.qmd After downloading the latest quarto version (1.6), the page does rotate to landscape when braces are put around an R chunk in 08_tables.qmd!
• rotating the flextable (no option for this; only rotating text, which doesn't update the placement of the headers)
• Putting latex commands inside an R chunk instead of outside, like this:

  cat(\newpage)
  cat(\blandscape)
  indices_table
  cat(\elandscape)
  cat(\newpage)

Ideas that have shown promise:

1. Adding the 3 latex packages in the skeleton yaml under the "header-includes" line, and wrapping a plot chunk (e.g., label: 'tbl-indices-plot') in these lines, as explained in this post:

\newpage
\blandscape
Landscape

summary(cars)

\elandscape

This forces the R chunk to be plotted in a landscape-oriented page, and creates output like this:

2. Adding code like this to that same chunk in 08_tables.qmd (replacing the above summary(cars) line), so that if the table is wider than the rotated page, the text is shrunken so that the table can fit in the landscape page.

Example code:

# set page width in inches
page_width <- 7.5

# identify flextable width
table_width <- flextable::flextable_dim(indices_table)[["widths"]] |> as.numeric()

if (table_width > page_width){
  indices_table <- indices_table |>
    flextable::fit_to_width(max_width = page_width )

  indices_table
} else {
  indices_table
}

This creates output like this:

3. After updating quarto to the latest version (1.6) 🤦 : Using the quarto landscape braces in the 08_tables.qmd (putting them around the R chunk), and not needing any extra yaml additions to the skeleton under header-includes! Creates output like in note 2, above.

Helpful post explaining previous questions and solutions for implementing landscape page orientation in quarto

#2 could be a good option. We would just need to code it into the tables. This however does not help the users if they are making custom ones. This is a great start!

#2 could be a good option. We would just need to code it into the tables. This however does not help the users if they are making custom ones. This is a great start!

Turns out, I just needed to update quarto to get the landscape option to work 🤦 but it's much easier to use. It might be possible to automate the insertion of the landscape braces around the chunk if a table is too wide for portrait- will try this next. But I think we've hit a milestone of identifying how to switch a table's orientation from portrait to landscape, at least!

#2 could be a good option. We would just need to code it into the tables. This however does not help the users if they are making custom ones. This is a great start!

Turns out, I just needed to update quarto to get the landscape option to work 🤦 but it's much easier to use. It might be possible to automate the insertion of the landscape braces around the chunk if a table is too wide for portrait- will try this next. But I think we've hit a milestone of identifying how to switch a table's orientation from portrait to landscape, at least!

What version did you update it to?

#2 could be a good option. We would just need to code it into the tables. This however does not help the users if they are making custom ones. This is a great start!

Turns out, I just needed to update quarto to get the landscape option to work 🤦 but it's much easier to use. It might be possible to automate the insertion of the landscape braces around the chunk if a table is too wide for portrait- will try this next. But I think we've hit a milestone of identifying how to switch a table's orientation from portrait to landscape, at least!

What version did you update it to?

I updated the CLI to 1.6.40 (download page here). My quarto R package's version is 1.4.4.