Content Type - wiki
In discussion of using Drupal for CMS elsewhere, I had a brainy idea as someone objected that Drupal didn't supply a wiki. Thinking out the idea I suggested that perhaps a content type named wiki could be created where revisions are set and the content is published but not promoted where any authenticated user could edit the content. A menu block named Wiki could be created to associate the nodes to. A taxonomy list could be created to help find the wiki content. Let's see I would need a wiki content filter to apply to WikiWiki words. What am I missing? Perhaps a theme to separate the main content from the comments in a tabbed display similar to MediaWiki. What else? Earnie P.S.: I know I can use third party software with Drupal, I'm trying to think through this simplistic idea.
I have been using the Liquid Wiki Engine for Drupal 4.7.4. It has lots of bugs/issues, but it will work. I added wiki as a content type and it works great. The syntax is a bit off from media wiki (which most wiki users are used to). Please contact me if you have any questions about it. The module developers have not touched the projects in months. http://drupal.org/node/53517 Earnie Boyd wrote:
In discussion of using Drupal for CMS elsewhere, I had a brainy idea as someone objected that Drupal didn't supply a wiki. Thinking out the idea I suggested that perhaps a content type named wiki could be created where revisions are set and the content is published but not promoted where any authenticated user could edit the content. A menu block named Wiki could be created to associate the nodes to. A taxonomy list could be created to help find the wiki content. Let's see I would need a wiki content filter to apply to WikiWiki words.
What am I missing? Perhaps a theme to separate the main content from the comments in a tabbed display similar to MediaWiki. What else?
Earnie P.S.: I know I can use third party software with Drupal, I'm trying to think through this simplistic idea.
A taxonomy list could be created to help find the wiki content.
If you mean the system that will give wiki nodes a clean, readable path, I'd suggest this instead: A menu callback path (named "/wiki/" in the tradition of MediaWiki) which does a lookup on the concatenated path arguments. That way, a wiki article would always have a URL that is defined by its title (even if the title contains slashes). Issues that come with this: - Titles must be unique, which wiki_validate() would have to ensure. - Titles shouldn't be changeable without extra permissions, and triggering some "move" function that takes care of leaving a redirect page and things. Also, redirects - The question is whether you implement them in the way MediaWiki does (mirroring the target content) or by actually sending a 3xx HTTP response. But one note: This shouldn't be part of the core until it has really matured and is widely used. Until then, it would be just an add-on module, and I'm not sure this list is the right place for that. But this is my first message to this list, so don't trust the advice of the noob. ;) On 2/1/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
In discussion of using Drupal for CMS elsewhere, I had a brainy idea as someone objected that Drupal didn't supply a wiki. Thinking out the idea I suggested that perhaps a content type named wiki could be created where revisions are set and the content is published but not promoted where any authenticated user could edit the content. A menu block named Wiki could be created to associate the nodes to. A taxonomy list could be created to help find the wiki content. Let's see I would need a wiki content filter to apply to WikiWiki words.
What am I missing? Perhaps a theme to separate the main content from the comments in a tabbed display similar to MediaWiki. What else?
Earnie P.S.: I know I can use third party software with Drupal, I'm trying to think through this simplistic idea.
-- Aran
folks, we have lots of priori thinking on this feature already. Please continue the conversation at http://groups.drupal.org/wiki. that site also has a basic wiki page implementation.
On 2/1/07, Moshe Weitzman <weitzman@tejasa.com> wrote:
folks, we have lots of priori thinking on this feature already. Please continue the conversation at http://groups.drupal.org/wiki. that site also has a basic wiki page implementation.
Right, we are using this in the Dojo group! It's great and I have experimented with some class notes using wiki syntax. I was a little unsure, though, about what would be "standard" and how others (who all seem to be using "pure html") would take to editing pages I made in Markdown or other wiki dialects. One question: could you export the CCK wiki type (or is it a moduele)? I would love to know more about it! Victor Kane http://awebfactory.com.ar
Quoting Arancaytar Ilyaran <arancaytar.ilyaran@gmail.com>:
A taxonomy list could be created to help find the wiki content.
I mean help the user find the relative content.
If you mean the system that will give wiki nodes a clean, readable path, I'd suggest this instead:
A menu callback path (named "/wiki/" in the tradition of MediaWiki) which does a lookup on the concatenated path arguments. That way, a wiki article would always have a URL that is defined by its title (even if the title contains slashes).
Sound much like a path alias to me.
Issues that come with this: - Titles must be unique, which wiki_validate() would have to ensure.
Which could be done with a path alias, only one can exist.
- Titles shouldn't be changeable without extra permissions, and triggering some "move" function that takes care of leaving a redirect page and things.
Path aliases could help with this as well.
Also, redirects - The question is whether you implement them in the way MediaWiki does (mirroring the target content) or by actually sending a 3xx HTTP response.
A job for Global Redirect.
But one note: This shouldn't be part of the core until it has really matured and is widely used. Until then, it would be just an add-on module, and I'm not sure this list is the right place for that.
So far the only ``add-on'' is a blog entry explain how to do it.
But this is my first message to this list, so don't trust the advice of the noob. ;)
Ooo... Someone else to harrass. ;p Earnie
On Thursday February 1 2007 6:18 am, Earnie Boyd wrote:
In discussion of using Drupal for CMS elsewhere, I had a brainy idea as someone objected that Drupal didn't supply a wiki. Thinking out the idea I suggested that perhaps a content type named wiki could be created where revisions are set and the content is published but not promoted where any authenticated user could edit the content. A menu block named Wiki could be created to associate the nodes to. A taxonomy list could be created to help find the wiki content. Let's see I would need a wiki content filter to apply to WikiWiki words.
What am I missing? Perhaps a theme to separate the main content from the comments in a tabbed display similar to MediaWiki. What else?
Earnie P.S.: I know I can use third party software with Drupal, I'm trying to think through this simplistic idea.
Third party software is unnecessary: http://drupal.org/project/pearwiki_filter http://drupal.org/project/freelinking The above two are being used on http://groups.drupal.org/ http://wiki.bryght.com/wiki/wiki-recipe-for-freelinking-module -- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.kubuntu.org/ Drupal Fanatic: http://drupal.org/
I've struggled with both approaches - trying to integrate with MediaWiki and using plugins like Liquid or pear-wiki. I've come to the conclusion that integrating with MediaWiki isn't a sustainable approach. It requires too much hacking on both sides and the result still isn't seamless. That said, the Drupal Wiki modules leave a lot to be desired. I'm currently trying to improve pear-wiki to my application's needs. Liquid appears to be dead unfortunately, so pear-wiki + freelinking seems to be the best option right now and I'd encourage anyone considering any development in this area to contribute to these projects. Jason Flatt wrote:
On Thursday February 1 2007 6:18 am, Earnie Boyd wrote:
In discussion of using Drupal for CMS elsewhere, I had a brainy idea as someone objected that Drupal didn't supply a wiki. Thinking out the idea I suggested that perhaps a content type named wiki could be created where revisions are set and the content is published but not promoted where any authenticated user could edit the content. A menu block named Wiki could be created to associate the nodes to. A taxonomy list could be created to help find the wiki content. Let's see I would need a wiki content filter to apply to WikiWiki words.
What am I missing? Perhaps a theme to separate the main content from the comments in a tabbed display similar to MediaWiki. What else?
Earnie P.S.: I know I can use third party software with Drupal, I'm trying to think through this simplistic idea.
Third party software is unnecessary: http://drupal.org/project/pearwiki_filter http://drupal.org/project/freelinking The above two are being used on http://groups.drupal.org/ http://wiki.bryght.com/wiki/wiki-recipe-for-freelinking-module
On Thursday 01 February 2007 07:15, Keath Milligan wrote:
currently trying to improve pear-wiki to my application's needs. Liquid
As the author of the pear wiki module I would be interested what you are trying to improve on the module. About Drupal and wiki: have you seen my test-wiki at http://test.tschannen.net ? It allows collaborative editing, diff-view, list of recent changes, mediawiki and tikiwiki syntax (others would be possible but are not activated)
It allows collaborative editing, diff-view, list of recent changes, mediawiki and tikiwiki syntax (others would be possible but are not activated)
This is quite nice - I wonder if you could rig up the recentchanges.module via a View instead. -- Morbus Iff ( i put the demon back in codemonkey ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus
On Thursday 01 February 2007 09:24, Morbus Iff wrote:
This is quite nice - I wonder if you could rig up the recentchanges.module via a View instead.
The problem is that with 'View' you have a list of nodes. The recent changes block on the other hand is a list of revisions. This is not possible with views to my understanding of it. Additionally I plan to integrate also comments into recent changes, so you have a list of node-revisions and comments. This is the equivalent of a change on a Talk-page of Mediawiki.
Additionally I plan to integrate also comments into recent changes, so you have a list of node-revisions and comments. This is the equivalent of a change on a Talk-page of Mediawiki.
Awesome - keep us (or me, at least) informed of this. I've started very preliminary work this morning on an importer for converting MediaWiki to Drupal. It'll be a lOOng time (due to lack thereof) before it's ready, but it's definitely an area I'm moving in. -- Morbus Iff ( hey britney, you say you want to lose control? ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus
On Thursday 01 February 2007 09:49, Morbus Iff wrote:
Awesome - keep us (or me, at least) informed of this. I've started very preliminary work this morning on an importer for converting MediaWiki to Drupal. It'll be a lOOng time (due to lack thereof) before it's ready, but it's definitely an area I'm moving in.
I have now implemented that you also see comments on the recent changes list. The module on the test page is updated. Also a package to download is attached: http://test.tschannen.net/wiki/revision_history I will publish this module on drupal.org when I find the time.
this is great work, Julian, wiki support for development and project collaboration sites (together with project and project issues) will be making for great software development distros of drupal (or for any collaborative project). On 2/1/07, Julian <julian@tschannen.net> wrote:
On Thursday 01 February 2007 09:49, Morbus Iff wrote:
Awesome - keep us (or me, at least) informed of this. I've started very preliminary work this morning on an importer for converting MediaWiki to Drupal. It'll be a lOOng time (due to lack thereof) before it's ready, but it's definitely an area I'm moving in.
I have now implemented that you also see comments on the recent changes list. The module on the test page is updated. Also a package to download is attached:
http://test.tschannen.net/wiki/revision_history
I will publish this module on drupal.org when I find the time.
It allows collaborative editing, diff-view, list of recent changes, mediawiki and tikiwiki syntax (others would be possible but are not activated)
What handles the "Add tagging" block on the right? -- Morbus Iff ( i think the "good book" is missing some pages ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus
On Thursday 01 February 2007 09:25, Morbus Iff wrote:
What handles the "Add tagging" block on the right?
A custom module which allows flickr-like tagging. It is similar to 'community_tags' or 'taxonomy_user' but both of them are not yet available for drupal 5 and they didn't provide all the functionality I needed. But the module is not yet in a state that it is usable by others.
Wow. I didn't realize Drupal could be capable a wiki. Thanks for the heads up. On 2/1/07, Julian <julian@tschannen.net> wrote:
On Thursday 01 February 2007 07:15, Keath Milligan wrote:
currently trying to improve pear-wiki to my application's needs. Liquid
As the author of the pear wiki module I would be interested what you are trying to improve on the module.
About Drupal and wiki: have you seen my test-wiki at http://test.tschannen.net ?
It allows collaborative editing, diff-view, list of recent changes, mediawiki and tikiwiki syntax (others would be possible but are not activated)
-- Proud member of the KEXP cubicle army. http://www.cubiclearmy.com
Your suggestions are excellent for partitioning the wiki content, and even leaves the door open for multiple but separate wikis on the same system. For filtering (automatic CamelCase discovery and [[Title Discovery]] and [[ http://example.com|click here]] URL's, I have been using the freelinking module, now also available for 5.0. I have had quite good results with it. There was a pear-wiki module mentioned somewhere which I think supported different wiki syntax dialects, but I have never tried it (might be more powerful in the end). Victor Kane http://awebfactory.com.ar On 2/1/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
In discussion of using Drupal for CMS elsewhere, I had a brainy idea as someone objected that Drupal didn't supply a wiki. Thinking out the idea I suggested that perhaps a content type named wiki could be created where revisions are set and the content is published but not promoted where any authenticated user could edit the content. A menu block named Wiki could be created to associate the nodes to. A taxonomy list could be created to help find the wiki content. Let's see I would need a wiki content filter to apply to WikiWiki words.
What am I missing? Perhaps a theme to separate the main content from the comments in a tabbed display similar to MediaWiki. What else?
Earnie P.S.: I know I can use third party software with Drupal, I'm trying to think through this simplistic idea.
What am I missing?
Most probably a Google search on the words drupal wiki . The first result is the wiki project on drupal.org and the fifth is http://groups.drupal.org/wiki which is where the discussions are.
Quoting Karoly Negyesi <karoly@negyesi.net>:
What am I missing?
Most probably a Google search on the words drupal wiki . The first result is the wiki project on drupal.org and the fifth is http://groups.drupal.org/wiki which is where the discussions are.
But conversations cannot be made by using Google searching. The reason I posted to the list was to converse about the idea. So I might have found g.d.o/wiki using google. I still would have posted to this list. Sometimes development happens here. Earnie
But conversations cannot be made by using Google searching. The reason I posted to the list was to converse about the idea. So I might have found g.d.o/wiki using google. I still would have posted to this list. Sometimes development happens here.
But you have essentially forked the conversation. Could you please do the community a service and collect the ideas fom here and post them to g.d.o/wiki to unify the conversation again?
participants (11)
-
Arancaytar Ilyaran -
Earnie Boyd -
Jason Flatt -
Julian -
Karoly Negyesi -
Keath Milligan -
Matthew Lechleider -
Morbus Iff -
Moshe Weitzman -
Victor Kane -
Will Wyatt