Convert TWIKI to IPYNB

Turn TWIKI files into IPYNB. A Jupyter notebook with the text in Markdown cells; only code blocks with the class code become code cells, and outputs are empty.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop TWIKI files on the dialor turn it to pick what to do

A notebook built from your TWiki topic.The text lands in Markdown cells. Code blocks with the class code become code cells.

  1. What you get

    A Jupyter notebook in one IPYNB file. The text of the topic sits in Markdown cells, so headings and prose read as notes in the notebook.

    Only code blocks with the class code become code cells. Their outputs are empty.

  2. What changes

    WikiWords become links to topic names. Macros such as %TOC% and %DATE% are left out.

    Topic metadata lines such as %META:TOPICINFO stay as text. HTML written in the topic is shown as text, not applied.

  3. Where to go next

    For other paths from this format, see every TWIKI conversion. For other ways to produce notebooks, see every IPYNB conversion.

TWIKI and IPYNB.What each format is.

The formats

From · TWIKI

TWiki Markup

TWiki and Foswiki topic markup from company intranets and project wikis.

Extensions
.twiki
MIME type
text/x-twiki
Kind
Text and data
To · IPYNB

Jupyter Notebook

Jupyter notebooks. Code cells, their outputs and Markdown notes in one JSON file.

Extensions
.ipynb
MIME type
application/x-ipynb+json
Kind
Text and data

In your code.The same TWIKI to IPYNB conversion through the API, for your app or your agent.

terminal
$ cv convert report.twiki report.ipynb
$ cv convert report.twiki report.ipynb

Questions.What people ask about TWIKI to IPYNB.

01OF 04

No. Only code blocks with the class code become code cells. The rest of the text stays in Markdown cells.

No. Outputs are empty in every code cell.

Macros such as %TOC% and %DATE% are left out of the notebook.

HTML written in the topic is shown as text.

More conversions.Other ways in and out of TWIKI and IPYNB.