Convert TWIKI to MD
Turn TWIKI files into Markdown. GitHub Markdown with headings, lists, tables, links and footnotes.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TWIKI files on the dialor turn it to pick what to do
Wiki topics as GitHub Markdown.Headings, lists, tables, links and footnotes carry over from TWiki markup.
What you get
One Markdown file in GitHub style. Headings, lists, tables, links and footnotes from the TWiki or Foswiki topic are written as their Markdown equivalents.
WikiWords become links to topic names, so references between topics in the wiki stay as links in the output.
What changes or stays as text
Macros such as %TOC% and %DATE% are left out of the Markdown. Nothing is generated in their place.
Topic metadata lines such as %META:TOPICINFO stay in the file as plain text. HTML written in the topic is shown as text too, not interpreted as markup.
Next steps
Once the topics are Markdown, merge MD can join them. To see what else the format converts to, browse every MD conversion.
TWIKI and MD.What each format is.
The formats
TWiki Markup
TWiki and Foswiki topic markup from company intranets and project wikis.
- Extensions
- .twiki
- MIME type
- text
/x -twiki - Kind
- Text and data
Markdown
Plain text with light markup for headings, lists, links and code. What agents and developers write in.
- Extensions
- .md .markdown .mdown
- MIME type
- text
/markdown - Kind
- Text and data
In your code.The same TWIKI to MD conversion through the API, for your app or your agent.
$ cv convert report.twiki report.md$ cv convert report.twiki report.mdQuestions.What people ask about TWIKI to MD.
Yes. Tables and footnotes are part of the GitHub Markdown output, along with headings, lists and links.
They are left out. The Markdown file has no table of contents or date in their place.
Topic metadata lines stay as text. They are not removed or turned into anything else.
It is shown as text in the Markdown file. It is not kept as working HTML.