replacing static-site-generator with Tiki

Hi Gour,

Nice to see you back!

Interesting to read the pros and cons of SSGs. I'd love Tiki to become a
SSG:
https://dev.tiki.org/Static-Site-Generator

About more standard markup: We discussed this at the recent TikiFest:
https://tiki.org/TikiFest2018-Montreal#Wiki_Parsers_and_WYSIWYG

We can't change our text syntax every few Tiki versions. But it's been 16
years since Tiki started, and the Web is a very different place. So we
could move to something else and have something like a 5 year overlap where
Tiki syntax and something else would be supported. And people would get
another 5 years via a Long Term Support version. Or maybe we support both
forever. There would be a selector on each page, so editors could start new
pages with new syntax and progressively convert old pages. Some tools can
be added to assist but these things need manual review.

A very good thing is that our 150+ wiki plugins are all very consistent and
wouldn't need to change. So we "just" need to worry about the wiki markup
like bold, italic, etc.
We need a new Parser https://dev.tiki.org/Wiki-Parser-Revamp

Any initiative must be done taking into account the rich text editor
aspect: http://wysiwygproblems.com/
So we should find and improve upon a widely used text format with solid
Rich Text Editor support. CKEditor says they will now support this:
https://medium.com/content-uneditable/ckeditor-5-the-future-of-rich-text-editing-2b9300f9df2c


One generally accepted idea at the TikiFest is to add a wiki plugin for
CommonMark
https://packagist.org/packages/league/commonmark

So the following could be used all over Tiki:
{COMMONMARK()}
This is [an example](http://example.com/ "Title") inline link.

[This link](http://example.net/) has no title attribute
{COMMONMARK}

It will be interesting to see if/how people will use, and how it would
interact with other wiki plugins.


About offline editing: Next logical step is:
https://dev.tiki.org/Progressive-Web-App

WikiLingo is dead. Was an experiment. It demonstrated that it's easy to the
simple cases, but it's very hard to cover a full syntax. Won't we coming
back. A new experiment is welcome though.

"chat app to provide simple support for visitors" Please see:
https://doc.tiki.org/XMPP
https://github.com/igniterealtime/webmeet/blob/master/README.md
http://wikisuite.org/Why-Openfire



Best regards,

Marc

-- 
Marc Laporte

http://WikiSuite.org
http://PluginProblems.com
http://Avan.Tech
http://tiki.org


On Friday, September 28, 2018, Saša Janiška <gour-XQYBc/g6bItWk0Htik3J/[email protected]> wrote:

> Hello,
>
> I was playing with Tiki several years ago and almost migrated to it, but
> then, for whatever reasons deployed other stuff and used
> static-site-generators i(SSG)recently.
>
> However, although SSG is nice, providing clean markup markup, fast site
> etc., there is problem that one has to use some custom search solution
> (or pay for 3rd aprty service), then there is a question of commenting
> system for those wanting not to be tied with Disqus...same thing with
> form processing, chat app to provide simple support for visitors,
> integrate some sort of calendar for tracking events etc.
>
> This is the territory where Tiki does really shine and besides that atm
> I do not have a clue how to customize Tiki themes in order to avoid
> having another typical Bootstrap site (jay to BSfez!!), there is
> something which troubles me even more and that's writing of the
> content...
>
> There is no need to explain (considering my usage of SSG) that I'm
> accustomed to use my preferred editor (Emacs) and write using some
> 'standard' markup like rst/asciidoc/markdown and take advantage of
> editor's help in the form of helper functions, syntax high. etc., so
> wonder if there is some workaround in TIki to be able to writen offline
> and not having WYSIWYG online editor only?
>
> There is some support for Tiki markup in Pandoc in the form of "reader"
> so one can use Tiki markup to export content into some other markup
> forms, but I do lack a "writer" to allow me to some some 'standard'
> markup I'm accustomed to (e.g. reStructuredText) and convert into Tiki
> via simple copy&paste...I have asked for it
> (https://github.com/jgm/pandoc/issues/4825) so if someone consider it
> can be helpful for Tiki community, please comment!
>
> Iirc, there was also wikiLingo (https://github.com/wikiLingo/wikiLingo)
> initiative, but it looks it's stalled?
>
>
> Sincerely,
> Gour
>
> --
> The intricacies of action are very hard to understand.
> Therefore one should know properly what action is,
> what forbidden action is, and what inaction is.
>


-- 
Marc Laporte

http://WikiSuite.org
http://PluginProblems.com
http://Avan.Tech

_______________________________________________
TikiWiki-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-users