Wiki vs SharePoint | The Coffeehouse

BrianLy

z2bass wrote:
Yes, but it is a wiki engine

It's NOT an 'engine' in the sense that it doesn't process markup on the server side. Makes it impossible to generate tables of content or create wiki macros for advanced users.

JChung2006

Isshou wrote:
I've never worked with SharePoint myself.

QFE. Commenting about a platform you've never worked with is a bit much. SharePoint has many strengths, but its wiki implementation has room for improvement.

RussellW

I realize that this might constitute threadjacking, but there are so few discussions on Sharepoint Services wiki.

I am currently using the wiki, which is simply OK. Lots to be desired, but decent enough.

What I really need is a way to move some pages from one site to another. I am using Sharepoint Services 3.0. Conventional support channels have not helped me. There does not seem to be any way to do this through the Sharepoint web interface, nor the web folders interface. All of my wiki pages are template ASPX files without the content.

Does anyone have any insight on this problem (moving wiki pages) or know the proper forum to ask such a question?

Thanks in advance

populate

In reply to Keskos

#Jul 27th, 2004 @ 10:07 AM

SharePoint wiki is for emplyees, executives and ALL. Using SharePoint you will found ten thousand nice colaboration features with office suits.

More colaboration 3rd party software is avilable to bridge between LotusNotes, or SAP or any online business line. Anything you may think, is avialable in SharePoint Smiley

nanda.kumar

In reply to SlackmasterK

#Mar 30th, 2007 @ 8:09 PM

Its really kinda hard to work on Sharepoint, you need to make sure that you have your own IT guy who is much more experienced in using Sharepoint,

If you are looking for Enterprise class Wiki, make sure you try etouch's Samepage- if you need more info on this please let me know
my email ID nanda.kumar@royalchallengers.com

bohappa

In reply to nanda.kumar

#Apr 14th @ 1:53 PM

This thread is a bit dated. Wikis, as collaboration platforms, have emerged as direct competitors of SharePoint. SharePoint 2007 includes a wiki though I have not used it. I'd still rather use a wiki-based platform. MindTouch Deki, for example, provides an open API on which community members build extensions that are easily shared. in this way, a Deki instance can provide many features like forums, project management, and file management that SharePoint provides. My company has both, SharePoint and Deki. I take care of Deki and a number of SharePoint users have asked to use the wiki for project sites because they couldn't figure out how to achieve their goal in SharePoint. My suspicion is that SharePoint requires an active IT group to evangelize and support it.