items

contenttype based items

are items based on a mimetype. e.g. wiki markup, an image

We have them since some time in moin-2

items for markup functions (convertor (macro, parsers))

Some ideas to keep markup for functions (convertor (macro, parsers)) in moin-2 simple.

In moin-1 we need different markups in parsers implemented to call macros or other parsers. This is always an extension to the used markup language. Because of the already given syntax probably some parser must use a different syntax. For Example we don't have implemented to call the wiki parser in rest format.

Currently I think about if it is better to have just an item mimetype for functions. By this we can define that always one markup is valid by calling for example a macro. Also it simplifies setting acl rights on that function by doing it for the item. And it gives the possibility to use meta of that function item without interfering to the item where the macro is called.

The function item becomes then transcluded at the position where we want the function shown its result. This will need only markup to do the transclusion.

We could prepare such a function items for each macro (parser) with acl default rights. If a user wants them with different rights, parameters, he could change the defaultw or duplicate and change it then. For example we could show default values as meta key value pairs.

And the parameters can be overwritten by query string entered as transclusion parameter.

I think that makes macros highly configurable with default settings and changeable from within the wiki.

CK

A simple solution for CK is to show just a list of these function items and insert them by a click