-
**Is your feature request related to a problem? Please describe.**
We are migrating one of our projects and would like to build a few pages but not have them show up in the Table of Contents (TOC).…
mmcky updated
3 years ago
-
Now that @AakashGfude has merged in a unified CLI for building single pages, I feel like we could improve our documentation around the single-page use case to make it a bit more visible. While buildin…
-
We should document the conventions used when writing a `_config.yml` file in more detail. There was some discussion in PR ExecutableBookProject/cli#73 around specifying `latex` options to see if we sh…
mmcky updated
4 years ago
-
Following up on #21, it would be great if there was some way of annotating cells that _are_ expected to error.
Ideally, the build system would take that to mean that a cell errors if and only if it i…
-
Chapter 10 page 134 of Cybernetic Music
FORM is a function that captures APL (J in our use case) commands. It does so in a musical outline structure.
As a section of music can have subsections. FOR…
-
**Is your feature request related to a problem? Please describe.**
No
**Describe the solution you'd like**
When code cells are rendered, there should be a way to show line numbers. This could…
-
Since VSCode doesn't support cell tags (https://github.com/microsoft/vscode-jupyter/issues/1121), and we want the documentation to hide the code.
-
### Bug description
I believe Quarto (or maybe Pandoc) is getting confused by the [Grid](https://quarto.org/docs/authoring/tables.html#grid-tables)-style of specifying a table. Maybe because the tabl…
-
For the Python and R RSE books we essentially had to document the logical progression of steps involved in data processing / package development in a generic, teachable manner. One of the main things …
-
Please add audience tracking (suggestion box) a la Slido to our book. Check --> https://www.sli.do/
Maybe use the space on the far right of the page for this (but check how the book reads on a smar…