I have never understood why the "In[5]" and "Out[5]" in jupyter have to be so prominent, even in a output like this.
It seems useful to denote REPL input vs output, and to be able to identify output relating to input.
Show HN: A tool to convert Jupyter notebooks to beautiful blogs
11–20 of 38 posts
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#12Neat! Anyone working on projects to improve the share-ability, code review, version control, or web rendering of Jupyter notebooks, feel free to reach out to me when looking for an enthusiastic early user. Jupyter has been a game changer for my productivity as a data scientist, but I still struggle with something that seems as simple as "what's the best way to expose this to other people easily without having to set…
https://github.com/mwouts/jupytext looks like something you might enjoy. I'm not affiliated with the project in any way.
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#13Offtopic; does anyone know a tool that can turn a directory of source code into a nicely formatted PDF/PS? So with syntax highlighting etc based on the file you have and chapter index based on directory structure for instance?
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#14Neat! Anyone working on projects to improve the share-ability, code review, version control, or web rendering of Jupyter notebooks, feel free to reach out to me when looking for an enthusiastic early user. Jupyter has been a game changer for my productivity as a data scientist, but I still struggle with something that seems as simple as "what's the best way to expose this to other people easily without having to set…
If you send me an email (dan@kaggle.com) I'd love to set up a time to show you some mockups that may be the solution you are looking for.
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#15Did something go wrong here?
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#16I have never understood why the "In[5]" and "Out[5]" in jupyter have to be so prominent, even in a output like this.
It seems useful to denote REPL input vs output, and to be able to identify output relating to input.
Sure, but the [5] feels unnecessary in a finished document like this. I mean, the output should be right after the input anyway, right?
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#17Earlier quoted context omitted.
Two projects I've been watching with interest are https://kyso.io/for-teams and http://reviewnb.com .
ReviewNB is very promising! I just wish it could live within Github (my idea is something like how Zenhub reorganizes issues into a Kanban board - add a tab that only allows viewing of ipynb files), since right now I have to kind of cajole people to review notebooks on their site.
I am the developer behind ReviewNB.
> I just wish it could live within Github
Whenever I thought of integrating the review experience in the GitHub UI (via browser extension), I always thought of overwriting the GitHub diff UI. That approach is very hacky and would result in the extension stability issues (any DOM change in GitHub diff could break the extension).
But I just looked at Zenhub and having a separate tab for notebook review could actually work! Since it relies only on the tab related HTML, the extension would be relatively stable. There's still a question of how to post comments etc. But it might be a good start to just offer notebook diff in a separate GitHub tab for pull requests.
Thanks @the_watcher.
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#18Earlier quoted context omitted.
It seems useful to denote REPL input vs output, and to be able to identify output relating to input.
Sure, but the [5] feels unnecessary in a finished document like this. I mean, the output should be right after the input anyway, right?
It's so it's easy to refer to things, like equation numbers in a maths book, or line numbers in code. E.g. people talking about someone's notebook here on HN can be specific and clear.
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#19Earlier quoted context omitted.
ReviewNB is very promising! I just wish it could live within Github (my idea is something like how Zenhub reorganizes issues into a Kanban board - add a tab that only allows viewing of ipynb files), since right now I have to kind of cajole people to review notebooks on their site.
I am the developer behind ReviewNB. > I just wish it could live within Github Whenever I thought of integrating the review experience in the GitHub UI (via browser extension), I always thought of overwriting the GitHub diff UI. That approach is very hacky and would result in the extension stability issues (any DOM change in GitHub diff could break the extension). But I just looked at Zenhub and having a separate tab…
Glad you saw this!
Re: Show HN: A tool to convert Jupyter notebooks to beautiful blogs
#20Earlier quoted context omitted.
Is it tough to manually convert the md and use a CMS like Ghost or Hugo for website? Alternatively, exporting HTML and publishing can also help right? I'm curious why did you say so. Moreover did you check the recently released `voila` package that lets you publish Jupyter notebooks?
There are a bunch of ways that make it _possible_ to do all of this. What's really missing is a way to make it as easy as committing code to Github repo without having to do anything more than install a Github extension. Right now, I do my work in a notebook, it's automatically converted to a Markdown file (for code review), and I use nbconvert to generate static html, which gets deployed to an internal docs site. I'…
> and is still fairly unpolished (but very promising!).
I'm all ears. Please write to me at amit@reviewnb.com
I built ReviewNB and push improvements almost every single day :)