
![]() |
Show Changes |
![]() |
Edit |
![]() |
|
![]() |
Recent Changes |
![]() |
Subscriptions |
![]() |
Lost and Found |
![]() |
Find References |
![]() |
Rename |
![]() |
Administration Page |
| Search |
History
| 9/12/2007 10:19:35 AM |
| -76.30.20.161 |
| 9/12/2007 9:53:02 AM |
| -66.78.121.139 |
![]() |
List all versions |
FlexWiki already has an elegant way of managing discussion pages without needing to make major changes to the core engine.
The key to this would be to use the topic include capability, explained in IncludeFormattingRules.
{{TopicToBeIncluded}}
or
@@topic.TopicToBeIncluded._Body@@
Normally the page being discussed would have limited numbers able to perform edits, while the discussion page would be much less restricted. Doing this will let the discussion page always show the current version of the topic without cluttering the actual topic with noise. When a discussion page is created the original topic should have a See_Also: property defined that provides a link to that discussion page.
The discussion page would use the name of the topic being discussed with 'Discuss' as a suffix, e.g. DiscussionPageImplementationDiscuss. This is similar to adding Demo or Type to WikiTalk class topics to provide additional relevant material.
Does this proposal have merit? - JohnDavidson
I think so except I think duplicating the post at the top creates clutter and is unnecessary. If someone wants to read the topic they can visit the topic page. By duplicating it, it creates problems to the user about which one is the official page. And search engines will index the topic discussion page with the topic included and that will create more confusion. What would be useful is to have tabs at the top (in theory) to go back and forth between the topic and the topic discussion page with clearly segregated material. -- AstralisLux