This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Replies: 4 comments 1 reply
|
Not sure if these address the issues you raise, but various packages out there aid in publishing notebooks online, e.g. quarto |
0 replies
|
Can we integrate google colab? |
0 replies
|
@daemon-reconfig I believe this is actually something we tried a while back, but couldn't get working, but others can correct me if I'm wrong. The problem is that Google just doesn't want other apps linking with Colab, or so it would seem. |
0 replies
|
how about quilljs? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In getting the opportunity to work with Nikhil this week on a couple articles, I think our system of using Jupyter notebooks is an ingenious way of harnessing the power of Python without needing complicated embeds or the use of third-party tools like Streamlit. However, a couple downsides jumped out at me, and I think we could handle these negatives in order to strengthen how we utilize Jupyter notebooks moving forward.
package-lock.jsonfile present in NPM development environments. It also meant that I faced strange issues creating the table in the second article.All reactions