# Recommended workflow for creating and maintaining Jupyter tutorials. Weave?

**URL:** <https://discourse.julialang.org/t/recommended-workflow-for-creating-and-maintaining-jupyter-tutorials-weave/8163>\
**Category:** General Usage\
**Created:** [January 4, 2018, 6:51pm UTC](https://discourse.julialang.org/t/recommended-workflow-for-creating-and-maintaining-jupyter-tutorials-weave/8163 "2018-01-04T18:51:36Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [January 15, 2018, 11:04pm UTC](https://discourse.julialang.org/t/recommended-workflow-for-creating-and-maintaining-jupyter-tutorials-weave/8163/21 "2018-01-15T23:04:44Z")

</div>

Since ipynb filed are just JSON and the code and markdown cells are stored as plain text, I find the git diffs to be pretty readable as long as images (base64-encoded) were not changed. I like editing them in the browser, because that means I can test the code “live” and see markdown/latex rendering immediately for each cell rather than having to render the whole document.

[Previous page](https://discourse.julialang.org/t/recommended-workflow-for-creating-and-maintaining-jupyter-tutorials-weave/8163.md?page=1)