-
Notifications
You must be signed in to change notification settings - Fork 14
Better layout options for lessons with jupyter notebooks #10
Comments
I notice that the notebooks eg in this lesson: It would be useful if the split window could be resized; at the moment the Jupyter notebook is a little bit cramped. I appreciate UI elements may be way down the list of things to do, but being able to tear off tabs and rearrange them, eg as per JupyterLab, might make sense for some use cases. At the moment, for cases where markdown scripts are in the left hand panel and commands are "thrown across" to the terminal in the panel to the right makes complete sense; but there may be certain forms of instruction where having guidance in the top part of the screen and terminals in the lower third, or two terminals in separate windows side by side in the lower third, may make sense? |
This is great feedback. I should have closed this issue, since it originally was opened well before we offered jupyter notebooks as lesson guides, as shown in your screenshot above. However, I'll keep it open given your feedback and will rename appropriately. There are several high-profile tasks that need to take priority, but I'm hoping to have more time to commit to improving the layout in the near future. |
A lot of changes have been made to the front-end in the past year, and I think the new layout gives a lot more real estate. It's not as dynamic as the ideas discussed above, but it definitely does a lot to give more space to lesson content. One thing that's also supported today is a mobile layout, which collapses the lesson guide into its own tab. Perhaps we could support an option that forces this layout on all screen sizes if the author deems it necessary. |
Having Jupyter notebooks in the right pane isn't super useful, especially considering it leaves the lab guide totally blank. Might be better to move the jupyter notebook to the left somehow, even if through an optional parameter provided by the lab definition
The text was updated successfully, but these errors were encountered: