Working on my personal knowledge base... I want to format my documents, even on local hard disk in wiki syntax. Sometimes I would upload them to a (corporate) wiki, sometimes I would download them from there. Planned are some tools to support this flow and searching my knowledge base (documents) for later. Obviously I want the markdown to be compatible with most, minimising conversion work.
So my question is similar to this related question, but
Wiki. js is an open source wiki application that provides excellent Markdown support.
Markdown is a plain text formatting syntax aimed at making writing for the internet easier. The philosophy behind Markdown is that plain text documents should be readable without tags mussing everything up, but there should still be ways to add text modifiers like lists, bold, italics, etc.
When you go into the editing view of a wiki page, on the right hand side you will see a plus sign. Clicking on it will provide a short list of formatting codes as a help. You can edit this and custom design it for your worksite.
The MediaWiki markup language (commonly referred to within the MediaWiki community as wikitext, though this usage is ambiguous within the larger wiki community) uses sometimes paired non-textual ASCII characters to indicate to the parser how the editor wishes an item or section of text to be displayed.
Wikipedia says that there is no commonly accepted standard wikitext language.
Creole is one effort for a "common wiki markup language to be used across different Wikis". There is a version 1.0 of the specification and several wikis and wiki engines implement it. MediaWiki does not implement it.
Markdown has a large number of implementations and seems to be used quite a lot.
As there is no agreed standard, the language might be selected depending on features and available implementations depending on the use case.
(1) While there are a lot of wiki markups I suggest to stick to well defined markup language.
There are only 3 plain text markup with well defined specs:
Textile markup didn't gain well defined specs and has weak community around. I recommend consider above 3 options instead.
(2) You definitely should stick to plain text files.
Support software for all above formats able to produce high quality output for printing and on-line publishing.
I stick to RST because I need extendibility and ability to inline foreign markup (math with LaTeX, graph with graphviz/dot, plotting with imagemagic, etc)
I search over personal tips inside Emacs editor or inside bash/grep. For advertising purpose I publish my tips online, for example: http://tips.defun.work/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With