Title: Hi HN! I’m Rowan and with my co-founder Steve we are building Curvenote (<a href="https:&#x2F;&#x2F;curvenote.com" rel="nofollow">https:&#x2F;&#x2F;curvenote.com</a>) — a technical writing tool for sharing data analysis and research from Jupyter with a wider audience.<p>We are building Curvenote to get science communication out of PDFs and help researchers and data-scientists communicate interactive, reproducible results (graphs, figures, maps, etc.) that are linked to the actual data and computation. There are currently two parts to Curvenote: 1) a WYSIWYG collaborative writing environment for interactive, technical documents; and 2) a Jupyter integration that adds version control and commenting and can link interactive plots and outputs directly into Curvenote documents (including any new versions or comments on those outputs).<p>Steve and I met in the open-source&#x2F;science community and are coming at this from different angles: Steve has led data science teams, and keeping stakeholders and team members in the loop with up-to-date figures&#x2F;reports took a lot of time (via emails, screenshots, PPT presentations, customer reports, etc.) — leading to what he calls communication chaos. A lot of my experience is coming from writing a PhD thesis, writing papers, presenting early research to colleagues&#x2F;supervisors, and developing educational&#x2F;training material around open-source projects.<p>In both our experiences, there is a collaboration gap between working on data science (for us in Jupyter) and getting feedback or enabling other people on our teams to remix the work, add context or ask questions. We each had a lot of hacked-together solutions, that mostly cut out anyone who wasn’t comfortable in git or Jupyter. Curvenote aims to span this gap by providing tools that enable less technical (or busier) collaborators as well as integrations into anywhere Jupyter lives (e.g. AWS Sagemaker, JupyterHub, locally). We are aiming for the collaboration experience of Google Docs, the precise presentation of LaTeX, and first class integrations into computational notebooks - without changing data science tools.<p>The weaving of computational results into documents and keeping all the links pointing back to your Jupyter notebook cells starts to build an interconnected knowledge graph (similar to Notion or what Roam are doing for personal knowledge databases) — with a heavy focus on research, where ideas, equations, figures, code can be browsed, filtered and discovered. This starts to become a “web of science” — with very granular ways to address and remix content across projects. I get really excited about this. A lot of content I was producing during my PhD was shared between various presentations&#x2F;reports as I developed ideas over many years; I wanted to see how the ideas were linked together and allow other people (and myself!) to reuse parts of the work with the same ease as importing a software library.<p>We are seeing people producing their lab-group meeting notes [1], writing reports that can be shared inside their companies [2], reproducing research papers [3], writing computational textbooks [4], and cross-importing data-science visualizations across projects. Curvenote has a free tier for public projects and we charge $15&#x2F;user&#x2F;month for teams.<p>Our other inspiration is coming from distill.pub [5] and explorable explanations [6]. We are trying to make it really easy to create and share these types of interactive documents and connect them to computational environments. A lot of the components underlying our platform are open-source (see <a href="https:&#x2F;&#x2F;curvenote.dev" rel="nofollow">https:&#x2F;&#x2F;curvenote.dev</a>), including our editor which you can try without signing up [7]. We also have an active Slack community [8], with a broad user base: teachers, scientists, data scientists, data journalists. You&#x27;re welcome to join!<p>Really excited to get some feedback from the HN community - happy to talk more on version control of Jupyter Notebooks, about our open-source article editor, about explorable explanations, and would love to hear if some of the challenges we have faced around collaboration in data science&#x2F;research resonate with you?<p>[1] <a href="https:&#x2F;&#x2F;curvenote.com&#x2F;@simpeg&#x2F;meeting-notes&#x2F;2021-02-24" rel="nofollow">https:&#x2F;&#x2F;curvenote.com&#x2F;@simpeg&#x2F;meeting-notes&#x2F;2021-02-24</a><p>[2] <a href="https:&#x2F;&#x2F;curvenote.com&#x2F;@stevejpurves&#x2F;computational-finance&#x2F;modern-portfolio-theory" rel="nofollow">https:&#x2F;&#x2F;curvenote.com&#x2F;@stevejpurves&#x2F;computational-finance&#x2F;mo...</a><p>[3] <a href="https:&#x2F;&#x2F;curvenote.com&#x2F;@lheagy&#x2F;pixels-and-their-neighbours&#x2F;pixels-and-their-neighbours" rel="nofollow">https:&#x2F;&#x2F;curvenote.com&#x2F;@lheagy&#x2F;pixels-and-their-neighbours&#x2F;pi...</a><p>[4] <a href="https:&#x2F;&#x2F;curvenote.com&#x2F;@geosci&#x2F;inversion-module&#x2F;inverse-theory-overview" rel="nofollow">https:&#x2F;&#x2F;curvenote.com&#x2F;@geosci&#x2F;inversion-module&#x2F;inverse-theor...</a><p>[5] <a href="https:&#x2F;&#x2F;hn.algolia.com&#x2F;?dateRange=all&amp;page=0&amp;prefix=false&amp;query=distill.pub&amp;sort=byPopularity&amp;type=story" rel="nofollow">https:&#x2F;&#x2F;hn.algolia.com&#x2F;?dateRange=all&amp;page=0&amp;prefix=false&amp;qu...</a><p>[6] <a href="https:&#x2F;&#x2F;hn.algolia.com&#x2F;?dateRange=all&amp;page=0&amp;prefix=false&amp;query=explorable%20explanations" rel="nofollow">https:&#x2F;&#x2F;hn.algolia.com&#x2F;?dateRange=all&amp;page=0&amp;prefix=false&amp;qu...</a><p>[7] Editor demo here without signing up: <a href="https:&#x2F;&#x2F;curvenote.github.io&#x2F;editor&#x2F;" rel="nofollow">https:&#x2F;&#x2F;curvenote.github.io&#x2F;editor&#x2F;</a><p>[8] <a href="https:&#x2F;&#x2F;slack.curvenote.dev" rel="nofollow">https:&#x2F;&#x2F;slack.curvenote.dev</a>
Upvote: