-
Notifications
You must be signed in to change notification settings - Fork 313
add a table of contents object #98
Comments
The way to handle the references is probably with some kind of box that could be in an executable python cell that we'd just drop after the referring text. For example, something like this (but obviously less hideous): This is similar to what I have in mind for #76. |
@gregcaporaso that solution should be pretty straight-forward. I might have time this week to work on that if you'd like. |
All chapters currently have issues with the chapter label. See here. One of the pieces of metadata associated with each chapter should ultimately be its GitHub issue number. |
Here's a prototype of what the data frame TOC might ultimately look like. I'm going to keep this updated and use it until we have a page with all of this information. The columns in this spreadsheet that say "Inherit from issue labels" are ones that we won't want to include in the object, but rather that we'll want to pull from GitHub when we show this table on the project website. |
This is now complete as part of #140 and through gregcaporaso/build-iab. |
This would probably be a
pd.DataFrame
with a multi-index, but I need a single object that I can query to get chapter names and links, rather than hard-coding these through-out the text. This might be a little clunky because you can't execute python code in a markdown cell, but that will be better than having broken links and outdated chapter names scattered throughout the text.The text was updated successfully, but these errors were encountered: