History: Tiki-Flavored Markdown

• «
• »

            ! {{page}}

New in ((Tiki25)) is an option to use Tiki Flavored Markdown, which is essentially [https://github.github.com/gfm/|GitHub Flavored Markdown] (GFM) with additional syntax, which itself is essentially CommonMark with additional syntax, which itself is a standardized Markdown.

GFM is a strict superset of CommonMark. All the features which are supported in GitHub user content and that are not specified on the original CommonMark Spec are hence known as extensions, and highlighted as such.

CommonMark is a "A strongly defined, highly compatible specification of Markdown": https://commonmark.org/

It is since a few years, the [https://en.wikipedia.org/wiki/De_facto_standard|de facto standard] for textual syntax.

!! Why did Tiki move to this?
Tiki has always supported Open Standards. In such a standard existed when Tiki start, we would have used it.


!! History
When Tiki started in 2002, there was no standard for textual syntaxes. So the Tiki community, like other wiki engines just invented a syntax.

In 2006, wiki engines got together to elaborate a standard:
* http://www.wikicreole.org/
* https://en.wikipedia.org/wiki/Creole_(markup)

And Tiki was on board with moving to a standard:
* https://dev.tiki.org/item1781-Support-for-the-Wiki-creole-markup-syntax
* http://www.wikicreole.org/wiki/TikiWikiCMSGroupware

Some believed that WYSIWYG editors would make this need go away. We didn't see how that was possible:
* ((tw:Why Wiki Syntax Is Important))
* https://wysiwygproblems.com/

Unfortunately, MediaWiki didn't adopt Wiki Creole, and given its huge market hare (It powers Wikipedia and many other projects), Wiki Creole didn't gather significant adoption.

It seemed inevitable that a wiki/textual syntax would eventually become a de facto standard. But which ones? MediaWiki's syntax? 
* https://en.wikipedia.org/wiki/AsciiDoc (started in 2002)
* https://en.wikipedia.org/wiki/Markdown (started in 2004)
* https://en.wikipedia.org/wiki/ReStructuredText (started in 2002)

Or one of the many others?:
https://en.wikipedia.org/wiki/Lightweight_markup_language




In 2019, ((Tiki20)) added the possibility to add CommonMark to a section of a page: ((PluginMarkdown))

In 2022, ((Tiki25)) added the possibility to add Tiki Flavored Markdown by default to all content.



!! The Future
Next steps:
* Tiki Flavored Markdown will become the default syntax at one point.

What will happen to Tiki syntax?

For the foreseeable future, it will remain an option in Tiki
* The code is stable so we don't need to invest time on it.
* 2 decades of Tiki users have content using it. Migration is just too much work.

However, development and innovation will shift to Tiki Flavored Markdown so over time, there will be more and more incentive to migrate.

!! FAQ
!!! Is it possible to use Tiki Flavored Markdown for new content, while old content remains in Tiki syntax.
Yes, this is the default behavior.

!!! What parser does Tiki use?
[https://packagist.org/packages/league/commonmark|league/commonmark] which has over 115 million downloads.

!!! Why didn't Tiki move to something else sooner?
Changing wiki syntax is one of the most disruptive thing you can do to a wiki engine. It affects all the content. And it affects all the users. Thus, it is a huge quantity of work, and has the risk of alienating members of the community (they feel it imposes work on them, and they don't see the benefits).

It's acceptable to do a change like this every 10 or 15 years. So you need to be confident in your decision.

And while CommonMark has become the ''de facto'' standard, the [https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287|spec has still not reached 1.0].