Not sure where to start - wiki syntax module
I administer an installation of Drupal that runs the intranet website for a corporate help desk. The people that I have to help with content contribution just flat don't get HTML, and don't want to learn. A few of them know mediawiki formatting syntax, and so I thought this would be a viable solution to allow the unwashed masses to contribute content.
The other thing I wanted to do was to programatically generate a menu, or table of contents, for any node by default, allowing the use of a --NOTOC-- line or some thing like that to disable the menu.
The problem is, I'm not real sure where to begin. I've thought about defining my own content type for this, but then thought it might serve our needs better to apply the wiki style to the default content types.
Mostly I'm looking for suggestions/direction from more experienced Drupallers than I.
Wiki filters
There are several input filters that follow various wiki formats such as MediaWiki (including other modules), TWiki, and others.
You should probably also look at the pathauto module.
I would make your own content type as the default, and then specify one of the above filters to work with it depending on ease-of-use. There is no WYSIWYG for wiki input filters at this time.
I'm not sure if there is a TOC either. This is one of the items on my feature list for TWikifilter.
I wasn't expecting to get an
I wasn't expecting to get an answer, so I continued looking for how I could do what I wanted to do, and stumbled across hook_nodeapi() and hook_filter(). I got a real simple skeleton working for myself yesterday.
I perused the modules that you listed, and it looks like nodeapi and filter are the way to go. Thanks for the links to the modules, between those and the api docs I'm making pretty good headway.
As far as a WYSIWYG editor - that shouldn't be "too" hard to implement, and it may be something I'll look into in the near future. My biggest concerns are menu creation and formatting filters. I see a lot of the work has been done for me already, but I like to work it all out myself, I walk away with a better understanding of Drupal.
Thanks for the reply, it was very helpful :)