X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/7762cd5711f7d020901ee40dac972ec170919807..4ff8a41f07ef9839e8d701bf8b1b81c5b500ab53:/doc/todo/plugin.mdwn?ds=inline

diff --git a/doc/todo/plugin.mdwn b/doc/todo/plugin.mdwn
index e36f1e3ca..6525f5982 100644
--- a/doc/todo/plugin.mdwn
+++ b/doc/todo/plugin.mdwn
@@ -15,15 +15,4 @@ Suggestions of ideas for plugins:
   content. It also needs to update pages when related pages are added,
   so it needs to register dependencies pre-emptively between pages,
   or something. It's possible that this is a special case of backlinks and
-  is best implemented by making backlinks a plugin somehow. --[[Joey]]
-
-## case study: Moin Moin plugins
-
-See <http://moinmoin.wikiwikiweb.de/MoinDev/PluginConcept>
-
-6 different types of plugins:
-
-* *actions* are possibly out of scope for ikiwiki, this is probably what it uses for cgi script type stuff. Unless ikiwiki wants to allow pluggable CGI script stuff, it doesn't need these.
-* *parsers* and *formatters* are basically what I've been calling [[PluggableRenderers]]. MoinMoin separates these, so that a page is parsed to (presumbly) some intermediate form before being output as html or some other form. That's a nice separation, but what to do about things like markdown that are both a parser and a formatter?
-* *macros* and *processors* are analagous to preprocessor directives. A processor can operate on a large block of text though.
-* *themes* should be irrellevant (ikiwiki has [[templates]]).
+  is best implemented by making backlinks a plugin somehow. --[[Joey]]
\ No newline at end of file