More minor page count tweaks & fixes
And re-convert with latest htmlbook
This commit is contained in:
		@@ -1,6 +1,6 @@
 | 
			
		||||
<section data-type="chapter" id="chp-quarto">
 | 
			
		||||
<h1><span id="sec-quarto" class="quarto-section-identifier d-none d-lg-block"><span class="chapter-title">Quarto</span></span></h1>
 | 
			
		||||
<section id="introduction" data-type="sect1">
 | 
			
		||||
<section id="quarto-introduction" data-type="sect1">
 | 
			
		||||
<h1>
 | 
			
		||||
Introduction</h1>
 | 
			
		||||
<p>Quarto provides a unified authoring framework for data science, combining your code, its results, and your prose. Quarto documents are fully reproducible and support dozens of output formats, like PDFs, Word files, presentations, and more.</p>
 | 
			
		||||
@@ -11,7 +11,7 @@ Introduction</h1>
 | 
			
		||||
</ol><p>Quarto is a command line interface tool, not an R package. This means that help is, by-and-large, not available through <code>?</code>. Instead, as you work through this chapter, and use Quarto in the future, you should refer to the Quarto documentation page at <a href="https://quarto.org/" class="uri">https://quarto.org</a> for help.</p>
 | 
			
		||||
<p>If you’re an R Markdown user, you might be thinking “Quarto sounds a lot like R Markdown”. You’re not wrong! Quarto unifies the functionality of many packages from the R Markdown ecosystem (rmarkdown, bookdown, distill, xaringan, etc.) into a single consistent system as well as extends it with native support for multiple programming languages like Python and Julia in addition to R. In a way, Quarto reflects everything that was learned from expanding and supporting the R Markdown ecosystem over a decade.</p>
 | 
			
		||||
 | 
			
		||||
<section id="prerequisites" data-type="sect2">
 | 
			
		||||
<section id="quarto-prerequisites" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Prerequisites</h2>
 | 
			
		||||
<p>You need the Quarto command line interface (Quarto CLI), but you don’t need to explicitly install it or load it, as RStudio automatically does both when needed.</p>
 | 
			
		||||
@@ -84,7 +84,7 @@ smaller |>
 | 
			
		||||
<p>To get started with your own <code>.qmd</code> file, select <em>File > New File > Quarto Document…</em> in the menu bar. RStudio will launch a wizard that you can use to pre-populate your file with useful content that reminds you how the key features of Quarto work.</p>
 | 
			
		||||
<p>The following sections dive into the three components of a Quarto document in more details: the markdown text, the code chunks, and the YAML header.</p>
 | 
			
		||||
 | 
			
		||||
<section id="exercises" data-type="sect2">
 | 
			
		||||
<section id="quarto-exercises" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Exercises</h2>
 | 
			
		||||
<ol type="1"><li><p>Create a new Quarto document using <em>File > New File > Quarto Document</em>. Read the instructions. Practice running the chunks individually. Then render the document by clicking the appropriate button and then by using the appropriate keyboard short cut. Verify that you can modify the code, re-run it, and see modified output.</p></li>
 | 
			
		||||
@@ -106,7 +106,7 @@ Visual editor</h1>
 | 
			
		||||
<p>The visual editor has many more features that we haven’t enumerated here that you might find useful as you gain experience authoring with it.</p>
 | 
			
		||||
<p>Most importantly, while the visual editor displays your content with formatting, under the hood, it saves your content in plain Markdown and you can switch back and forth between the visual and source editors to view and edit your content using either tool.</p>
 | 
			
		||||
 | 
			
		||||
<section id="exercises-1" data-type="sect2">
 | 
			
		||||
<section id="quarto-exercises-1" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Exercises</h2>
 | 
			
		||||
<!--# TO DO: Add exercises. -->
 | 
			
		||||
@@ -165,7 +165,7 @@ Source editor</h1>
 | 
			
		||||
</div>
 | 
			
		||||
<p>The best way to learn these is simply to try them out. It will take a few days, but soon they will become second nature, and you won’t need to think about them. If you forget, you can get to a handy reference sheet with <em>Help > Markdown Quick Reference</em>.</p>
 | 
			
		||||
 | 
			
		||||
<section id="exercises-2" data-type="sect2">
 | 
			
		||||
<section id="quarto-exercises-2" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Exercises</h2>
 | 
			
		||||
<ol type="1"><li><p>Practice what you’ve learned by creating a brief CV. The title should be your name, and you should include headings for (at least) education or employment. Each of the sections should include a bulleted list of jobs/degrees. Highlight the year in bold.</p></li>
 | 
			
		||||
@@ -341,7 +341,7 @@ comma(.12358124331)
 | 
			
		||||
</div>
 | 
			
		||||
</section>
 | 
			
		||||
 | 
			
		||||
<section id="exercises-3" data-type="sect2">
 | 
			
		||||
<section id="quarto-exercises-3" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Exercises</h2>
 | 
			
		||||
<ol type="1"><li><p>Add a section that explores how diamond sizes vary by cut, color, and clarity. Assume you’re writing a report for someone who doesn’t know R, and instead of setting <code>echo: false</code> on each chunk, set a global option.</p></li>
 | 
			
		||||
@@ -394,14 +394,14 @@ Other important options</h2>
 | 
			
		||||
<p>It’s a good idea to name code chunks that produce figures, even if you don’t routinely label other chunks. The chunk label is used to generate the file name of the graphic on disk, so naming your chunks makes it much easier to pick out plots and reuse in other circumstances (i.e. if you want to quickly drop a single plot into an email or a tweet).</p>
 | 
			
		||||
</section>
 | 
			
		||||
 | 
			
		||||
<section id="exercises-4" data-type="sect2">
 | 
			
		||||
<section id="quarto-exercises-4" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Exercises</h2>
 | 
			
		||||
<!--# TO DO: Add exercises -->
 | 
			
		||||
</section>
 | 
			
		||||
</section>
 | 
			
		||||
 | 
			
		||||
<section id="tables" data-type="sect1">
 | 
			
		||||
<section id="quarto-tables" data-type="sect1">
 | 
			
		||||
<h1>
 | 
			
		||||
Tables</h1>
 | 
			
		||||
<p>Similar to figures, you can include two types of tables in a Quarto document. They can be markdown tables that you create in directly in your Quarto document (using the Insert Table menu) or they can be tables generated as a result of a code chunk. In this section we will focus on the latter, tables generated via computation.</p>
 | 
			
		||||
@@ -499,7 +499,7 @@ Tables</h1>
 | 
			
		||||
<p>Read the documentation for <code><a href="https://rdrr.io/pkg/knitr/man/kable.html">?knitr::kable</a></code> to see the other ways in which you can customize the table. For even deeper customization, consider the <strong>gt</strong>, <strong>huxtable</strong>, <strong>reactable</strong>, <strong>kableExtra</strong>, <strong>xtable</strong>, <strong>stargazer</strong>, <strong>pander</strong>, <strong>tables</strong>, and <strong>ascii</strong> packages. Each provides a set of tools for returning formatted tables from R code.</p>
 | 
			
		||||
<p>There is also a rich set of options for controlling how figures are embedded. You’ll learn about these in <span class="quarto-unresolved-ref">?sec-graphics-communication</span>.</p>
 | 
			
		||||
 | 
			
		||||
<section id="exercises-5" data-type="sect2">
 | 
			
		||||
<section id="quarto-exercises-5" data-type="sect2">
 | 
			
		||||
<h2>
 | 
			
		||||
Exercises</h2>
 | 
			
		||||
<!--# TO DO: Add exercises -->
 | 
			
		||||
@@ -672,7 +672,7 @@ csl: apa.csl</pre>
 | 
			
		||||
</section>
 | 
			
		||||
</section>
 | 
			
		||||
 | 
			
		||||
<section id="learning-more" data-type="sect1">
 | 
			
		||||
<section id="quarto-learning-more" data-type="sect1">
 | 
			
		||||
<h1>
 | 
			
		||||
Learning more</h1>
 | 
			
		||||
<p>Quarto is still relatively young, and is still growing rapidly. The best place to stay on top of innovations is the official Quarto website: <a href="https://quarto.org/" class="uri">https://quarto.org</a>.</p>
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user