diff --git a/.gitignore b/.gitignore index 732e061..72ded39 100644 --- a/.gitignore +++ b/.gitignore @@ -9,4 +9,3 @@ inst/doc .httr-oauth tests/testthat/googlesheets_token.rds run_test.R -docs diff --git a/README.md b/README.md index 0f20cb9..6e8f5af 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,8 @@ `leanbuild` converts a [Bookdown repository](https://github.com/jtr13/bookdown-template) into a [Leanpub-ready](https://leanpub.com/) set of files. The output rendered files from this package can be published using the [Github writing mode on Leanpub](https://leanpub.com/lfm/read#leanpub-auto-switching-writing-modes). +[Read the full documentation here](https://jhudatascience.org/leanbuild/docs/index.html). + ## Required files: Before you are ready to run `leanbuild`, you will need the following files (which are standard in a `Bookdown` repository): diff --git a/docs/404.html b/docs/404.html new file mode 100644 index 0000000..4fb5e31 --- /dev/null +++ b/docs/404.html @@ -0,0 +1,160 @@ + + + +
+ + + + +Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+The GNU General Public License is a free, copyleft license for software and other kinds of works.
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
+When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
+For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
+For the developers’ and authors’ protection, the GPL clearly explains that there is no warranty for this free software. For both users’ and authors’ sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
+Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users’ freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
+Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
+The precise terms and conditions for copying, distribution and modification follow.
+“This License” refers to version 3 of the GNU General Public License.
+“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
+To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
+A “covered work” means either the unmodified Program or a work based on the Program.
+To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
+A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work’s System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+The Corresponding Source for a work in source code form is that same work.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures.
+You may convey verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
+An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party’s predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor’s “contributor version”.
+A contributor’s “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor’s essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient’s use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
+The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
+If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+END OF TERMS AND CONDITIONS
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
+<one line to give the program's name and a brief idea of what it does.>
+Copyright (C) 2018 John Muschelli
+
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
+If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
+Copyright (C) 2021 John Muschelli
+ leanbuild for details type 'show w'.
+ This program comes with ABSOLUTELY NO WARRANTY;
+ This is free software, and you are welcome to redistribute it'show c' for details. under certain conditions; type
The hypothetical commands show w
and show c
should show the appropriate parts of the General Public License. Of course, your program’s commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.
+The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
+leanbuild
converts a Bookdown repository into a Leanpub-ready set of files. The output rendered files from this package can be published using the Github writing mode on Leanpub.
If you aren’t familiar with Bookdown
you may want with their tutorials.
You can install leanbuild
from GitHub with:
You will need to use the remotes package (and will need to install it if you don’t have it).
++if (!("remotes" %in% installed.packages())) { + install.packages("remotes") +} +if (!("leanbuild" %in% installed.packages())) { + remotes::install_github("jhudsl/leanbuild") +}
Before you are ready to run leanbuild
, you will need the following files (which are standard in a Bookdown
repository):
+- a _bookdown.yml
file which lists the .Rmd
files that are to be rendered in a rmd:
category (see example file). - .Rmd
files which contain the chapter content (including your index.Rmd
file which Bookdown
has). - an images
directory that contains any images that are referenced in the chapters. - .bib
file(s) to complete any citation renders (see example file).
Optionally: - a Book.txt
file which lists the order of the chapters/quiz files (this can be autogenerated with leanbuild
) (see example file). - a directory containing quizzes in the form of .md
files which have been written using the Markua formatting specifications (see example folder).
Here’s an example of what the Bookdown file set up (which leanbuild will look for) might be set up like:
+A_Bookdown_Repo
+├── _bookdown.yml
+├── index.Rmd
+├── 01-chapter_one.Rmd
+├── docs
+│ └── ...
+├── references.bib
+├── quizzes
+│ ├── quiz_1.md
+│ └── ...
+├── resources/images
+│ ├── some-figures.png
+│ └── ...
+└── Book.txt
+If you’d like to use our example repository you can fork it on Github and clone it to your own computer Follow these instructions to fork and then you can clone it using a command line.
+But for the purposes of this example we will download a zip file of the files we need and set those up using this function:
++# Run this to get the files we need +example_files <- leanbuild::example_repo_setup()
Each of your Rmds needs to have a chunk of code with this at the beginning of the file: leanbuild::set_knitr_image_path()
This will ensure that the images are stored in the correct place and will be rendered correctly both in Bookdown
and in Leanpub.
The leanbuild
package converts your files using this main function (which we won’t run just yet).
leanbuild::bookdown_to_leanpub()
+By default, leanbuild
will re-run a bookdown::render_book("index.Rmd")
rendering of your chapters first before converting the files to the Leanpub ready format. It will only process the Rmd
files that are listed in the _bookdown.yml
file. However, if you wish to skip this step, you can set render = FALSE
when running the leanbuild::bookdown_to_leanpub()
function.
Leanpub’s Github writing mode will look for a directory called manuscript
to publish from. You should not edit the files in manuscript/
by hand since a re-run of leanbuild
will cause your changes to be overwritten.
Leanpub requires a Book.txt
file to know what order the chapters/quizzes should be published.
By default, your Book.txt
file will not be autogenerated but leanbuild
will look in your given directory for an existing Book.txt
file which it will copy over to the output directory.
You can create a Book.txt
file manually, or if your quizzes and chapters are numbered, leanbuild
can create the Book.txt
file based on the numbers going from low to high and quizzes following chapters of the same number. (e.g. quiz_03.md
will be placed after 03-some_chapter_file.Rmd
).
To have leanbuild
attempt to autogenerate this file with the main function you can set make_book_txt
to TRUE
. If no Book.txt
file is found and make_book_txt
is set to FALSE
(this is the default setting), leanbuild
will fail.
So to run the main function and also have it make a Book.txt
file for us, we can run the following:
+leanbuild::bookdown_to_leanpub(make_book_txt = TRUE)
## Looking for bookdown file in /home/rstudio/GitRepos/leanbuild/vignettes
+## Processing these files:
+## index.Rmd
+## 01-intro.Rmd
+## 02-example-chapter.Rmd
+## Rendering the Book
+## index_file is /home/rstudio/GitRepos/leanbuild/vignettes/index.Rmd
+## Warning in bookdown::render_book(input = index_file, output_format =
+## output_format, : The argument 'clean_envir' has been deprecated and will be
+## removed in future versions of bookdown.
+## /usr/lib/rstudio-server/bin/pandoc/pandoc +RTS -K512m -RTS Course_Name.md --to html4 --from markdown+autolink_bare_uris+tex_math_single_backslash --output Course_Name.html --lua-filter /usr/local/lib/R/site-library/bookdown/rmarkdown/lua/custom-environment.lua --lua-filter /usr/local/lib/R/site-library/rmarkdown/rmarkdown/lua/pagebreak.lua --lua-filter /usr/local/lib/R/site-library/rmarkdown/rmarkdown/lua/latex-div.lua --metadata-file /tmp/Rtmpsk0eRN/file2fa21ff74b3 --wrap preserve --citeproc --standalone --section-divs --table-of-contents --toc-depth 3 --template /usr/local/lib/R/site-library/bookdown/templates/gitbook.html --highlight-style pygments --number-sections --citeproc --include-in-header /tmp/Rtmpsk0eRN/rmarkdown-str2fa7f83a803.html --mathjax
+##
+## Output created: docs/index.html
+## Copying Resources
+## Copying Docs folder
+## Copying bib files
+## Autogenerated Book.txt saved to: manuscript/Book.txt
+## Leanpub ready files are saved to manuscript Go to https://leanpub.com/ to publish them using the GitHub writing mode.
+Alternatively, we could run bookdown_to_book_txt()
function on its own:
+leanbuild::bookdown_to_book_txt()
## Autogenerated Book.txt saved to: manuscript/Book.txt
+Also note that any index.Rmd
will always be placed first and any about.Rmd
file will be placed last.
We can take a peek at what the autogenerated file looks like. By default the Book.txt
file is saved to the manuscript
directory along with all the other Leanpub-ready files.
## [1] "index.Rmd" "01-intro.Rmd" "02-example-chapter.Rmd"
+First, we will set up a directory to put our quizzes in.
++quiz_dir <- "quizzes" +if(!dir.exists(quiz_dir)) { + dir.create(quiz_dir) +}
By default, leanbuild will look for a folder called quizzes/
to find your quiz .md
files. If your quizzes are located somewhere else, you will need to use the quiz_dir
argument to specify that:
leanbuild::bookdown_to_leanpub(quiz_dir = "some_other_directory")
+Leanpub can be very particular about the formatting of the quizzes, so there are funtions to help you check the formatting of your quiz.
+In the main argument, you can set run_quiz_checks
to TRUE
(the default is FALSE
).
leanbuild::bookdown_to_leanpub(run_quiz_checks = TRUE)
+But the quiz checks can also be run separately using the check_quizzes()
function. It will again assume you have a directory called quizzes
unless you specify otherwise:
We can take a look at how check_quizzes()
runs using a quiz examples: one that passes the checks and one that fails.
+# Set up an good example quiz +good_quiz_path <- leanbuild::good_quiz_path() + +dest_quiz_path <- file.path("quizzes", basename(good_quiz_path)) + +if (!file.exists(dest_quiz_path)){ + file.copy(from = good_quiz_path, + to = dest_quiz_path) +}
## [1] TRUE
+Run check_quizzes()
to check all quizzes in the directory.
+quiz_checklist <- leanbuild::check_quizzes(quiz_dir = "quizzes")
##
+## Checking quiz: quizzes/quiz_good.md
+## Checking question: First question to as ... in quiz: quiz_good.md
+## Checking question: Example without choo ... in quiz: quiz_good.md
+## Checking question: Question example wit ... in quiz: quiz_good.md
+## Checking question: A more complicated e ... in quiz: quiz_good.md
+##
+## No question errors to report!
+We can take a look at what a typical quiz format looks like:
+ +## [1] ""
+## [2] "{quiz, id: quiz_name_here, attempts: 10}"
+## [3] ""
+## [4] "## Template quiz"
+## [5] ""
+## [6] "Put any other instructions your quiz takers need to know here like, Choose the best answer."
+Now let’s add in a bad quiz and see how the report changes.
++# Set up an good example quiz +bad_quiz_path <- leanbuild::bad_quiz_path() + +dest_quiz_path <- file.path("quizzes", basename(bad_quiz_path)) + +if (!file.exists(dest_quiz_path)){ + file.copy(from = bad_quiz_path, + to = dest_quiz_path) +}
## [1] TRUE
+Let’s re-run check_quizzes()
.
+quiz_checklist <- leanbuild::check_quizzes(quiz_dir = "quizzes")
##
+## Checking quiz: quizzes/quiz_bad.md
+## Checking question: It would be a shame ... in quiz: quiz_bad.md
+## Warning in FUN(X[[i]], ...): Colon detected in question on lines: 7 in question
+## starting with:It would be a shame ... in quiz: quiz_bad.md
+## Checking question: What a shame if we p ... in quiz: quiz_bad.md
+## Checking question: Shame shame if we sa ... in quiz: quiz_bad.md
+## Checking question: What if we don't put ... in quiz: quiz_bad.md
+## Warning in FUN(X[[i]], ...): No correct answers provided for What if we don't
+## put ... in quiz: quiz_bad.md
+## Checking question: What if only give co ... in quiz: quiz_bad.md
+## Warning in FUN(X[[i]], ...): No incorrect answer options provided for What if
+## only give co ... in quiz: quiz_bad.md
+##
+## Checking quiz: quizzes/quiz_good.md
+## Checking question: First question to as ... in quiz: quiz_good.md
+## Checking question: Example without choo ... in quiz: quiz_good.md
+## Checking question: Question example wit ... in quiz: quiz_good.md
+## Checking question: A more complicated e ... in quiz: quiz_good.md
+##
+## Question error report saved to 'question_error_report.tsv'
+We have some warning messages about various items and the errors have been saved to 'question_error_report.tsv'
which we can read in and check out. Each line shows an error detected, what quiz file it was detected in, the line it’s roughly associated with and the warning message which explains what the problem is.
+error_df <- readr::read_tsv("question_error_report.tsv")
##
+## ── Column specification ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────
+## cols(
+## question_names = col_character(),
+## quiz = col_character(),
+## warning_msg = col_character(),
+## related_index = col_double()
+## )
+
+error_df
## # A tibble: 3 x 4
+## question_names quiz warning_msg related_index
+## <chr> <chr> <chr> <dbl>
+## 1 It would be a shame if we pu… quiz_… Colon detected in question… 7
+## 2 What if we don't put a corre… quiz_… No correct answers provide… 31
+## 3 What if only give correct an… quiz_… No incorrect answer option… 38
+Now you would just need to go into each of those files and fix the stated problem. Then you can re-run check_quizzes()
and see if the warning is resolved.
leanbuild
converts a Bookdown repository into a Leanpub-ready set of files. The output rendered files from this package can be published using the Github writing mode on Leanpub.
Before you are ready to run leanbuild
, you will need the following files (which are standard in a Bookdown
repository):
_bookdown.yml
file which lists the .Rmd
files that are to be rendered in a rmd:
category (see example file)..Rmd
files which contain the chapter content (including your index.Rmd
file which Bookdown
has).images
directory that contains any images that are referenced in the chapters..bib
file(s) to complete any citation renders (see example file).Optionally:
+Book.txt
file which lists the order of the chapters/quiz files (this can be autogenerated with leanbuild
) (see example file)..md
files which have been written using the Markua formatting specifications (see example folder).Here’s an example of what the Bookdown file set up (which leanbuild will look for) might be set up like:
+A_Bookdown_Repo
+├── _bookdown.yml
+├── index.Rmd
+├── 01-chapter_one.Rmd
+├── docs
+│ └── ...
+├── references.bib
+├── quizzes
+│ ├── quiz_1.md
+│ └── ...
+├── resources/images
+│ ├── some-figures.png
+│ └── ...
+└── Book.txt
+If you’d like to use our example repository you can fork it on Github and clone it to your own computer Follow these instructions to fork and then you can clone it using a command like:
+git clone https://github.com/{organization}/DaSL_Course_Template_Leanpub.git
+But replace {organization}
with the location of your forked repository.
You can install leanbuild
from GitHub with:
You will need to use the remotes package (and will need to install it if you don’t have it).
++if (!("remotes" %in% installed.packages())) { + install.packages("remotes") +} +remotes::install_github("jhudsl/leanbuild")
Each of your Rmds needs to have this chunk of code in the beginning of the file:
+```{r, include = FALSE}
+leanbuild::set_knitr_image_path()
+```
+This will ensure that the images are stored in the correct place and will be rendered correctly both in Bookdown
and in Leanpub.
The leanbuild
package converts your files using this main function:
leanbuild::bookdown_to_leanpub()
+By default, leanbuild
will re-run a bookdown::render_book("index.Rmd")
rendering of your chapters first before converting the files to the Leanpub ready format. However, if you wish to skip this step, you can set render = FALSE
when running the leanbuild::bookdown_to_leanpub()
function.
Leanpub requires a Book.txt
file to know what order the chapters/quizzes should be published.
By default, your Book.txt
file will not be autogenerated but leanbuild
will look in your given directory for an existing Book.txt
file which it will copy over to the output directory.
You can create a Book.txt
file manually, or if your quizzes and chapters are numbered, leanbuild
can create the Book.txt
file based on the numbers going from low to high and quizzes following chapters of the same number. (e.g. quiz_03.md
will be placed after 03-some_chapter_file.Rmd
).
To have leanbuild
attempt to autogenerate this file, set make_book_txt
to TRUE
.
leanbuild::bookdown_to_leanpub(make_book_txt = TRUE)
+If no Book.txt
file is found and make_book_txt
is set to FALSE
(this is the default setting), leanbuild
will fail.
A leanbuild autogenerated Book.txt
file might look something like this:
index.Rmd
+01-chapter.Rmd
+quiz_1.md
+02-chapter.Rmd
+quiz_2.md
+about.Rmd
+Also note that any index.Rmd
will always be placed first and any about.Rmd
file will be placed last.
By default, leanbuild will look for a folder called quizzes/
to find your quiz .md
files. If your quizzes are located somewhere else, you will need to use the quiz_dir
argument to specify that:
leanbuild::bookdown_to_leanpub(quiz_dir = "some_directory")
+NEWS.md
+ Declare file path to docs/ folder
+bookdown_destination(path = ".")+ +
path | +Where to look for the _bookdown.yml file. Passes toget_bookdown_spec() function. By default looks in current directory |
+
---|
The file paths to Rmds listed in the _bookdown.yml file.
+ +R/bookdown_to_leanpub.R
+ bookdown_rmd_files.Rd
Get file paths all Rmds in the bookdown directory
+bookdown_rmd_files(path = ".")+ +
path | +Where to look for the _bookdown.yml file. Passes toget_bookdown_spec() function. By default looks in current directory |
+
---|
The file paths to Rmds listed in the _bookdown.yml file.
+ +R/bookdown_to_leanpub.R
+ bookdown_to_book_txt.Rd
Create Book.txt file from files existing in quiz directory
+bookdown_to_book_txt( + path = ".", + output_dir = "manuscript", + quiz_dir = "quizzes", + verbose = TRUE +)+ +
path | +path to the bookdown book, must have a `_bookdown.yml` file |
+
---|---|
output_dir | +output directory to put files. It should likely be +relative to path |
+
quiz_dir | +Where are the quizzes stored? Default looks for folder called "quizzes". |
+
verbose | +print diagnostic messages |
+
A list of quiz and chapter files in order in a file called Book.txt -- How Leanpub wants it.
+ +Convert Bookdown to Leanpub
+bookdown_to_leanpub( + path = ".", + render = TRUE, + output_dir = "manuscript", + make_book_txt = FALSE, + quiz_dir = "quizzes", + run_quiz_checks = FALSE, + remove_resources_start = FALSE, + verbose = TRUE, + footer_text = NULL +)+ +
path | +path to the bookdown book, must have a `_bookdown.yml` file |
+
---|---|
render | +if `TRUE`, then [bookdown::render_book()] will be run on each Rmd. |
+
output_dir | +output directory to put files. It should likely be +relative to path |
+
make_book_txt | +Should [leanbuild::bookdown_to_book_txt()] be run +to create a `Book.txt` in the output directory? |
+
quiz_dir | +directory that contains the quiz .md files that should be +checked and incorporated into the Book.txt file |
+
run_quiz_checks | +TRUE/FALSE run quiz checks |
+
remove_resources_start | +remove the word `resources/` at the front +of any image path. |
+
verbose | +print diagnostic messages |
+
footer_text | +Optionally can add a bit of text that will be added to the +end of each file before the references section. |
+
A list of output files and diagnostics
+ +Takes output from [leanbuild::parse_quiz] and runs checks on each question in a quiz by calling [leanbuild::check_question] for each question. +First splits questions into their own data frame. Returns a list of messages/warnings about each question's set up.
+check_all_questions(quiz_specs, quiz_name = NA, verbose = TRUE)+ +
quiz_specs | +quiz_specs which is output from [leanbuild::parse_quiz]. |
+
---|---|
quiz_name | +The name of the quiz being checked. |
+
verbose | +Whether progress messages should be given. |
+
A list of the output from [leanbuild::check_question] with messages/warnings regarding each question and each check.
+ +++# Using good quiz md example + +quiz_path <- good_quiz_path() +good_quiz <- readLines(quiz_path) +good_quiz_specs <- parse_quiz(good_quiz) +good_quiz_checks <- check_all_questions(good_quiz_specs) +#>#>#>#>+# Using bad quiz md example + +bad_quiz <- readLines(bad_quiz_path()) +bad_quiz_specs <- parse_quiz(bad_quiz) +bad_quiz_checks <- check_all_questions(bad_quiz_specs) +#>#> Warning: Colon detected in question on lines: 7 in question starting with:It would be a shame ... in quiz: NA#>#>#>#> Warning: No correct answers provided for What if we don't put ... in quiz: NA#>#> Warning: No incorrect answer options provided for What if only give co ... in quiz: NA
Check quiz question set up to see if it is compliant with Leanpub and Coursera needs. +Based off of [Markua guide](https://leanpub.com/markua/read#leanpub-auto-quizzes-and-exercises). +Is called by [leanbuild::check_all_questions] and run for each question.
+check_question(question_df, quiz_name = NA, verbose = TRUE)+ +
question_df | +Which is an individual question's data frame after being parse from |
+
---|---|
quiz_name | +The name of the quiz the question is from |
+
verbose | +Whether progress messages should be given |
+
A list of messages/warnings regarding each check for the given question.
+ +++# Use readLines to read in a quiz +quiz_path <- good_quiz_path() +quiz_lines <- readLines(quiz_path) + +# Use group_split to get the questions +questions_df <- parse_quiz(quiz_lines)$data %>% + dplyr::group_split(question) + +good_quiz_checks <- check_question(questions_df[[2]]) +#>
For a file path to a quiz, check whether it is properly formatted for Leanpub.
+check_quiz(quiz_path, verbose = TRUE)+ +
quiz_path | +A file path to a quiz markdown file |
+
---|---|
verbose | +print diagnostic messages? TRUE/FALSE |
+
A list of checks. "good" means the check passed. Failed checks will report where it failed.
+ +++# Take a look at a good quiz's checks: +quiz_path <- good_quiz_path() +good_checks <- check_quiz(quiz_path) +#> +#>#>#>#>#>+# Take a look at a failed quiz's checks: +quiz_path <- good_quiz_path() +failed_checks <- check_quiz(quiz_path) +#> +#>#>#>#>#>
Check Quiz Attributes
+check_quiz_attributes(quiz_specs, quiz_name = NULL, verbose = TRUE)+ +
quiz_specs | +The output from [leanbuild::parse_quiz]. |
+
---|---|
quiz_name | +A character string indicating the name of the quiz being checked. |
+
verbose | +Would you like progress messages? TRUE/FALSE |
+
A logical
+ +This is ran automatically by [leanbuild::check_all_questions] for all questions. +It checks that the attributes specified are accepted ones by Leanpub.
+check_quiz_question_attributes(question_df, quiz_name = NULL, verbose = TRUE)+ +
question_df | +a data.frame obtained from [leanbuild::parse_quiz_df] and dplyr::group_split(question). |
+
---|---|
quiz_name | +inherited from parse |
+
verbose | +print diagnostic messages |
+
Check the formatting of all quizzes in a given directory.
+check_quizzes(quiz_dir = "quizzes", write_report = TRUE, verbose = TRUE)+ +
quiz_dir | +A path to a directory full of quizzes that should all be checked with [leanbuild::check_all_quizzes]. |
+
---|---|
write_report | +TRUE/FALSE save warning report to a CSV file? |
+
verbose | +print diagnostic messages |
+
A list checks performed on each quiz
+ +++ +## Make a temporary quiz directory +quiz_dir <- dirname(good_quiz_path()) + +## Now check the quizzes in that directory +all_quiz_results <- check_quizzes(quiz_dir = quiz_dir) +#> +#>#>#> Warning: Colon detected in question on lines: 7 in question starting with:It would be a shame ... in quiz: quiz_bad.md#>#>#>#> Warning: No correct answers provided for What if we don't put ... in quiz: quiz_bad.md#>#> Warning: No incorrect answer options provided for What if only give co ... in quiz: quiz_bad.md#> +#>#>#>#>#>#> +#>
R/coursera.R
+ convert_coursera_quizzes.Rd
Convert Leanpub md quiz to Coursera yaml quiz
+convert_coursera_quizzes( + input_quiz_dir = "quizzes", + output_quiz_dir = "coursera_quizzes", + verbose = TRUE +)+ +
input_quiz_dir | +A path to a directory of leanpub formatted quiz md files. By default assumes "quizzes" and looks in current directory. |
+
---|---|
output_quiz_dir | +A folder (existing or not) that the new coursera converted quizzes should be saved to. By default saves to "coursera_quizzes". |
+
verbose | +Would you like the progress messages: TRUE/FALSE? |
+
A folder of coursera ready quiz files saved to the output directory specified as a yamls.
+ +++# Set up a directory with a quiz in it for this example +tdir <- tempfile() +dir.create(tdir, showWarnings = FALSE, recursive = TRUE) + +file.copy(from = good_quiz_path(), + to = file.path(tdir, basename(good_quiz_path()))) +#> [1] TRUE+# Provide path to directory of quizzes +convert_coursera_quizzes(tdir) +#>#>#> [[1]] +#> NULL +#>
Convert a Leanpub-formatted md quiz file to a Coursera-formatted yaml quiz file in preparation for uploading to Coursera.
+convert_quiz(quiz_path, output_quiz_dir = dirname(quiz_path), verbose = TRUE)+ +
quiz_path | +A path to a quiz .md file to be converted. |
+
---|---|
output_quiz_dir | +An existing folder where you would like the new version of the quiz to be saved. +Default is the directory of the quiz_path provided |
+
verbose | +Would you like the progress messages? |
+
A Coursera-ready quiz file saved to the output directory specified as a yaml.
+ ++#>#>+ +
Convert youtube link
+convert_utube_link(utube_link)+ +
utube_link | +a link to a youtube video that may or may not be "www.youtube.com/embed" or "www.youtube.com/watch?v=" +format. |
+
---|
Returns a youtube link in the "watch" format so it will render properly in Leanpub or Coursera-friendly files
+ +Create a version of Leanpub that does not have a TOC and has quizzes in the Coursera yaml format. Requires Bookdown output files including "assets", "resources", and "libs".
+render_coursera( + output_dir = file.path("docs", "coursera"), + output_yaml = "_output.yml", + convert_quizzes = FALSE, + input_quiz_dir = "quizzes", + output_quiz_dir = "coursera_quizzes", + verbose = TRUE +)+ +
output_dir | +A folder (existing or not) that the TOC-less Bookdown for Coursera files should be saved. By default is file.path("docs", "coursera") |
+
---|---|
output_yaml | +A output.yml file to be provided to bookdown. By default is "_output.yml" |
+
convert_quizzes | +TRUE/FALSE whether or not to convert quizzes. Default is TRUE |
+
input_quiz_dir | +A path to a directory of Leanpub-formatted quiz md files. By default assumes "quizzes" and looks in current directory. |
+
output_quiz_dir | +A folder (existing or not) where the coursera quizzes should be saved. By default is "coursera_quizzes". |
+
verbose | +Would you like the progress messages? TRUE/FALSE |
+
A folder of coursera ready quiz files and html chapter files saved to output directories specified.
+ +Download Google Slides File
+download_gs_file(id, out_type = "pptx")+ +
id | +Identifier of Google slides presentation, passed to
+ |
+
---|---|
out_type | +output type of file to download. Usually +`pdf` or `pptx` |
+
Downloaded file (in temporary directory)
+This downloads presentations if they are public and also try to make +sure it does not fail on large files
+ +Clean up example repo files
+example_repo_cleanup(files_to_remove, verbose = FALSE)+ +
files_to_remove | +List of example files to delete. |
+
---|---|
verbose | +TRUE/FALSE would you like progress messages? |
+
++# Run this to get the files we need +example_files <- leanbuild::example_repo_setup() + +# Run this to delete them +example_repo_cleanup(files_to_remove = basename(example_files)) +#>#>#>#>#>#> Warning: cannot remove file 'docs', reason 'Directory not empty'#>#>#> Warning: cannot remove file 'manuscript', reason 'Directory not empty'#>#>#>#>#>#>#> Warning: cannot remove file 'resources', reason 'Directory not empty'#>#>#> [[1]] +#> [1] TRUE +#> +#> [[2]] +#> [1] TRUE +#> +#> [[3]] +#> [1] TRUE +#> +#> [[4]] +#> [1] FALSE +#> +#> [[5]] +#> [1] TRUE +#> +#> [[6]] +#> [1] FALSE +#> +#> [[7]] +#> [1] TRUE +#> +#> [[8]] +#> [1] TRUE +#> +#> [[9]] +#> [1] TRUE +#> +#> [[10]] +#> [1] TRUE +#> +#> [[11]] +#> [1] TRUE +#> +#> [[12]] +#> [1] FALSE +#> +#> [[13]] +#> [1] TRUE +#> +#> [[14]] +#> [1] TRUE +#> +#> [[15]] +#> NULL +#>+
Set up example repo files
+example_repo_setup(dest_dir = ".")+ +
dest_dir | +The destination directory you would like the example repo files to be placed. By default is current directory. |
+
---|
+# Run this to get the files we need +example_files <- leanbuild::example_repo_setup() + +
Extract meta fields from a tag
+extract_meta(tags)+ +
tags | +A single tag or vector of tags to extract the fields from. |
+
---|
A named vector indicating the field and entry associated with it.
+ +++### Simple example +tag <- "{quiz, id: quiz_name_here, attempts: 10}" + +# Extract metadata tags +meta <- extract_meta(tag) + +### Example using a file +quiz_path <- good_quiz_path() +quiz_lines <- readLines(quiz_path) + +# Put this in a data.frame so we can identify the content +quiz_df <- parse_quiz_df(quiz_lines) + +# Extract the tags +tags <- quiz_df %>% + dplyr::filter(type == "tag") %>% + dplyr::pull("original") + +# Extract metadata tags +meta <- extract_meta(tags) +
R/footnotes.R
+ footnotes.Rd
Convert Bookdown footnotes to Leanpub-formatted footnotes
+convert_footnotes(content)+ +
content | +a character vector containing the lines of content from a file read in with readLines() |
+
---|
a character vector containing the content given but with Leanpub formatted foonotes
+ +R/bookdown_to_leanpub.R
+ get_bookdown_spec.Rd
Load in Bookdown specifications from _bookdown.yml
+get_bookdown_spec(path = ".")+ +
path | +Where to look for the _bookdown.yml file. Passes to the bookdown_file() function. By default looks in current directory |
+
---|
The yaml contents using yaml::yaml.load_file()
+ +Get Slide ID from URL
+get_slide_id(x)+ +
x | +URL of slide |
+
---|
A character vector
+ ++x <- paste0( + "https://docs.google.com/presentation/d/", + "1Tg-GTGnUPduOtZKYuMoelqUNZnUp3vvg_7TtpUPL7e8", + "/edit#slide=id.g154aa4fae2_0_58" +) +get_slide_id(x) +#> [1] "1Tg-GTGnUPduOtZKYuMoelqUNZnUp3vvg_7TtpUPL7e8"
Get Google Slide PNG URL
+gs_png_url(url) + +get_slide_page(url) + +gs_png_download(url, output_dir = ".", overwrite = TRUE) + +include_slide( + url, + output_dir = knitr::opts_chunk$get("fig.path"), + overwrite = TRUE, + ... +)+ +
url | +URL to Google Slide |
+
---|---|
output_dir | +path to output png |
+
overwrite | +should the slide PNG be overwritten? |
+
... | +for |
+
A character vector of URLs
+ ++url <- paste0( + "https://docs.google.com/presentation/d/", + "12DPZgPteQBwgal6kSPP58zhPhjZ7QSPZLe3NkA8M3eo/edit", + "#slide=id.gc8648f14c3_0_397&t=4" +) +id <- get_slide_id(url) +gs_png_url(url) +#> [1] "https://docs.google.com/presentation/d/12DPZgPteQBwgal6kSPP58zhPhjZ7QSPZLe3NkA8M3eo/export/png?id=12DPZgPteQBwgal6kSPP58zhPhjZ7QSPZLe3NkA8M3eo&pageid=gc8648f14c3_0_397"
+ All functions+ + |
+ |
---|---|
+ + | +Path to bad example quiz |
+
+ + | +Declare file path to docs/ folder |
+
+ + | +Find file path to _bookdown.yml |
+
+ + | +Find main Bookdown directory |
+
+ + | +Get file paths all Rmds in the bookdown directory |
+
+ + | +Create Book.txt file from files existing in quiz directory |
+
+ + | +Convert Bookdown to Leanpub |
+
+ + | +Check all quiz questions |
+
+ + | +Check Quiz Question Set Up |
+
+ + | +Check Quiz |
+
+ + | +Check Quiz Attributes |
+
+ + | +Check a question's attributes |
+
+ + | +Check all quizzes in a directory |
+
+ + | +Convert Leanpub md quiz to Coursera yaml quiz |
+
+ + | +Convert Leanpub md quiz to Coursera yaml quiz |
+
+ + | +Convert youtube link |
+
+ + | +Create TOC-less Bookdown for use in Coursera |
+
+ + | +Download Google Slides File |
+
+ + | +Clean up example repo files |
+
+ + | +Set up example repo files |
+
+ + | +Extract meta fields from a tag |
+
+ + | +Convert Bookdown footnotes to Leanpub-formatted footnotes |
+
+ + | +Load in Bookdown specifications from _bookdown.yml |
+
+ + | +Get Slide ID from URL |
+
+ + | +Path to good example quiz |
+
+
|
+ Google Slides Helper Functions |
+
+
|
+ Get Google Slide PNG URL |
+
+ + | +Check Leanpub Course or Book |
+
+ + | +Parse apart a tag |
+
+ + | +Parse Quiz and Other Checking Functions |
+
+ + | +Parse quiz into a data.frame |
+
+ + | +Remove YAML header |
+
+ + | +Replace HTML and other Tags in Leanpub Markdown |
+
+ + | +Set image path for `knitr` |
+
+ + | +Run Simple References |
+
Parse apart a tag
+parse_q_tag(tag)+ +
tag | +A single tag to extract from |
+
---|
A named vector indicating the field and entry associated with it.
+ +++tag <- "{quiz, id: quiz_name_here, attempts: 10}" +parse_q_tag(tag) +#> [[1]] +#> {quiz, id +#> "quiz_name_here, attempts" +#>+
Parse Quiz and Other Checking Functions
+Extract lines of the quiz
+parse_quiz(quiz_lines, quiz_name = NULL, verbose = FALSE) + +extract_quiz(quiz_lines)+ +
quiz_lines | +A quiz's contents read in with readLines() |
+
---|---|
quiz_name | +A character vector indicating the name of the quiz. |
+
verbose | +Would you like progress messages? TRUE/FALSE |
+
A list of elements, including a `data.frame` and metadata +for questions
+the lines of the quiz that actually contain of the content of the quiz.
+ +++quiz_lines <- c( + "{quiz, id: quiz_00_filename}", + "### Lesson Name quiz", + "{choose-answers: 4}", + "? What do you think?", + "", + "C) The answer to this one", + "o) Not the answer", + "o) Not the answer either", + "C) Another correct answer", + "m) Mandatory different answer", + "", + "{/quiz}" +) +quiz_specs <- parse_quiz(quiz_lines) +check_quiz_attributes(quiz_specs) +#> [1] "good"+
Parse quiz into a data.frame
+parse_quiz_df(quiz_lines, remove_tags = FALSE)+ +
quiz_lines | +A character vector of the contents of the markdown +file obtained from readLines() |
+
---|---|
remove_tags | +TRUE/FALSE remove tags and empty lines? |
+
A data frame containing a type column which indicates what type of line each is.
+ +++# Use readLines() to read in a quiz +quiz_path <- good_quiz_path() +quiz_lines <- readLines(quiz_path) + +# Can use this to parse the quiz into a data.frame +quiz_df <- parse_quiz_df(quiz_lines) +
Remove YAML header
+remove_yaml_header(file)+ +
file | +file name of the markdown file |
+
---|
A character vector of the text without the YAML header
+ ++file <- system.file("extdata/00_template.Rmd", package = "leanbuild") +out <- remove_yaml_header(file) +#> Warning: file("") only supports open = "w+" and open = "w+b": using the former#> character(0)
Replace HTML and other Tags in Leanpub Markdown
+replace_html( + path = "manuscript", + remove_resources_start = TRUE, + footer_text = NULL, + fullbleed = FALSE, + verbose = TRUE +) + +replace_single_html( + file, + footer_text = NULL, + remove_resources_start = TRUE, + fullbleed = FALSE, + verbose = TRUE +)+ +
path | +path to the markdown files that need replacement. |
+
---|---|
remove_resources_start | +remove the word `resources/` at the front +of any image path. |
+
footer_text | +a bit of text that will be added to the +end of each file before the references section. |
+
fullbleed | +should the image have the attribute `fullbleed: true`? |
+
verbose | +print diagnostic messages |
+
file | +individual markdown file |
+
A list of output files and diagnostics
+ +Run Simple References
+simple_references(x, bib_files, add_reference_header = FALSE)+ +
x | +A filename of a markdown or Rmarkdown file, or the full output +from `readLines` on that file |
+
---|---|
bib_files | +bibliography files to use for pandoc |
+
add_reference_header | +Should the `## References` header be added at the +end of the output? |
+
A character vector of the file, with references subbed in
+ +