Re: [Tiki-devel] importing content
Saša Janiška <gour-XQYBc/g6bItWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.cms.tiki.user,gmane.comp.cms.tiki.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 5 Oct 2018 18:07:43 +0200 Torsten Fabricius <[email protected]> wrote: > adding Markdown as an option if it does not brake the current parser > would be quite nice. :-) > If any possible i would love to have it added similar as the WYSIWYG, > which stores the data in WikiSyntax and allows to use WikiPlugins > inside the CKE based WYSIWYG and WikiSyntax Editors. Today, while chatting with Bernard (Opening Hours) I mentioned to him the following project: https://github.com/hectorguo/CKEditor-Markdown-Plugin (there is also https://github.com/ckeditor/ckeditor5-markdown-gfm) which apparently brings markdown support to CKE, but I'm too ignorant to know atm how it us used/inegrated withing Tiki. > It would be great to then switch between the three editors WYSIWYG / > WikiSyntax / Markdown, all capable of parsing the same Wikiplugins. Dreamland! I know there is concern to keep parser for WIkiSyntax due to backward compatibilits, LTS issue etc., but otoh, I believe that using some of the PHP-markdown parsers listed here: https://dev.tiki.org/Wiki-Parser-Revamp would take the burden of maintaining one's own parser and leave Tiki devs to work on other features. For those users which do prefer WYSIWYG writing, there is still CKE, but those familiar to use non-WYSIWYG editor (aka WikiSyntax) could, with the time, switch to more standard markup like Markdown. Here I do not want to mention that Markdown support would certainly bring new users - between Grav CMS (~10K stars project, 2017 CMS Critic Award for Best Flat File CMS) and Tiki, the latter is superior to me due to its monolithic design (https://pluginproblems.com) > If we get this done right, then we should use this occassion for a > small (or big) marketing campaign! I'd say that it would deserve a big one!! > Not for coding, but for other stuff i could contribute after November > this year. Maybe we find a few more people to contribute to a/the > campaign!? If I see there is interest amongst Tiki dev to do it, iow. seeing it could be an important evolution in Tiki's lifetime, I'm ready to help/learn as much as I can, but if all this is just a "nice add-on" or as Marc wrote "not on my personal or business roadmap.", then I'll leave it here. I understand that Tiki is not just another CMS, but many of the today's most popular one are flat-file-bease and/or do support Markdown at least. (personally I don't have anything against usage of DB, ぶut flat-file CMS-es are, of course, easier to deploy.) Sincerely, Gour -- A self-realized man has no purpose to fulfill in the discharge of his prescribed duties, nor has he any reason not to perform such work. Nor has he any need to depend on any other living being. _______________________________________________ TikiWiki-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tikiwiki-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWDpE0TZF+khoOctpNyVpzrf8dgUFAlu3nlwACgkQNyVpzrf8 dgV9MQ/6AmH+8hoMoVtZSN6SJyvHMG3ZK+h+Lf+dX9ZdfTw9v/20D9x4l4NTaLPA b0Cr2KJDoM4efQ/un/SZ8hwrhsVj3YkuHMgqFZ+viaAcijFMGsirpQuV6QuP/es7 yfuag0t0GOFMOzRJ2Utlx5P1dBYaqelZMWHszAP4YjUbs9O2v1lhbUhjmjI8mbhU ZKo/191kSdlqtkrwTlnyRBxyhv39q6jwZmNfA79BZZIRHrGbsoeU3u/ZPVWI+ML8 cvAt9TStN6vUVGMDq0IOFdmwBO9m0UA+BUh9uO4mkXxgsAJuA6j7x2XJ91LkiVho SCfxS8NLvYqKrcOQGg7TOwfWW77RVjEn9pKohH/fpksTwxzZ0dkue7PGAo/rEP4b fzyqysF76thsSOhA+XMup8bx3SNDNF2Z3ZEfDP1/oQ3/yvekuOPCyBMNMZZ0Kf4i GrQhV9hXY2enQEAgSaZWeOH3luqVkbdmptGsQrALKiV9LdoUwG9Epqm/+FcOVAs+ QP2GPDl7/rjp7R/enDb98QR3HfOlOFoyxsBY1VJ8AXjZlLSIU1pZ+BacDyt2tWet b48wpB6x9XnwRc39C2WiKtJoCtP+gs4I6WWEbkE8d2kE/TIvtNc4oj1AdU/S/Vi8 wPnX9NIszfaYwBHgKW4StUwEiixCtItd3vZLfJfWJuSchQY+7yw= =01Yc -----END PGP SIGNATURE-----