Re: Sharepoint Wiki Information
- From: MBParker@xxxxxxxxxxxx
- Date: 15 Nov 2006 15:12:28 -0800
In response to your question and for others' benefit, here is
MY INTIAL REVIEW of the SHAREPOINT 2007 (latest b2?) WIKI (
http://37.freesharepoint2007.com/Wiki1 ):
The short is a quite impressive first start, especially with WYSIWYG
seemingly-HTML editor and even diffing & displaying changes in WYSIWYG.
However, also with some potentially show-stopper limitations which
would have been easy for Microsoft to fix but are hard impossible for
the end-user to fix - see below. Anyone know how to fix em?
As far as a manual, I notice it comes with minimal wiki page "How To
Use This Wiki" (
http://37.freesharepoint2007.com/Wiki1/How%20To%20Use%20This%20Wiki%20Library.aspx
) , which does include the one basic wiki formatting (linking) feature
of writing "[[<page name> |<link label>]]" to create a link to a
page (where "|<link label>" is optional), plus the ability to also
create pages implicitly from such links. All other textual formatting
seems to be handled (cleanly) by WYSIWYG (especially tables), although
HTML's annoying absolute sectioning (<h2> </h2> as opposed to
<section> </section>) is still not corrected. Unlike other wikis as
Trac, no macros are supported (for say calculated values, query result
inclusion, etc).
It maintains a history of all page content changes, and is easy to
revert back to any prior page.
And impressively (indeed, leaps & bounds above wikipedia -on THIS
point):
· it features a nice WYSIWYG editor, seemingly HTML;
· and can, unlike Word, seemingly produce & copy-out *clean* HTML
(Microsoft, what possibly came over you?),
· plus, very usefully, you can paste in HTML, such as a copy from a
web page.
· You can seemingly paste-in inline graphics (cool!).
· And, yes!, the editor can produce tables!
· And it can very elegantly & clearly show, with WYSIWYG formatting,
exactly what text has been added and deleted (at least paragraph text;
I haven't tried table cell changes) - quite impressive.
However, it can only compare (automatically diff) with the prior
version (unlike say wikipedia which can dynamically compare any two
versions).
I don't know if it's storing changes compactly (the current version
plus just diffs of the prior), which is important to make maintaining a
complete history efficient, especially for any large page.
Unfortunately, change to the title is seemingly not recorded in the
history (even though title is seemingly the most important descriptor).
And even though worse (see below, due to another problem) even a 1
character change in the title also causes catastrophic results to
external links & indexing (see below) .
Moreover, in a video about what the wiki would be from its MS
designers, inheriting from sharepoint lists, I recall them mentioning
all properties would be versioned (plus properties could be added),
making this Microsoft's first wiki unique, but I don't see any of this.
Moreover, unlike all other sharepoint lists, wikis seem to have only
the one built-in view (plus supplied diffing), and custom views
aren't offered (even via FrontPage/Sharepoint Designer?).
Also a maintenance headache, while internal links (at least from the
wiki) are corrected when the page is renamed, the their display text
isn't updated to reflect the new title (while not always, many times
this is very appropriate; if I change the name of something, I of
course want to change the displayed references to it (if they intend to
use the official name).
BUT MOST SERIOUSLY, even in the latest 2007 version, the wiki (and
seemingly all the rest of Sharepoint content) fails to use/have a
permanent URL for the page ID; this forces potentially long URLs, plus
and rename to the page title change the URL, breaking any external
links (including index ranking in search engines, as Google...!). This
may be the showstopper for me.
While the wiki can display the incoming links to a page, these aren't
displayable (a least a few of them) alongside the page (but in a
separate page) - this would be nice, especially for parent link pages,
though one could get into the habit of putting parent links into the
wiki (though it would be nice to automatically insure this).
On that note, and also VERY SERIOUS and essential for scalability, much
like the prior Sharepoint, no standards for navigation seem to be built
in (standard links for parent(s), children, previous, next, plus
path(s) to root, plus what-I-think-is-called bread-crumb trails (the
path you got here)).. And (to fix this and more), it doesn't seem
possible to customize the view (though maybe with Frontpage/Sharepoint
Designer - anyone know?).
Microsoft, please fix the above --for you, it should be easy.
And until then, anyone have any ideas on how to fix any of these?
Thanks, -Mike Parker, MIT CS Grad
--Helping develop the community database http://www.CommuniDB.com ,
to feature a wiki (and more) which pays its authors.
.
- Follow-Ups:
- Re: Sharepoint Wiki Information
- From: MBParker
- Re: Sharepoint Wiki Information
- References:
- Sharepoint Wiki Information
- From: jonny2d
- Re: Sharepoint Wiki Information
- From: Todd Klindt [MVP]
- Sharepoint Wiki Information
- Prev by Date: Re: Deleting users
- Next by Date: Re: On every list type support EVERY view! - how? (in Sharepoint 2007/v3)
- Previous by thread: Re: Sharepoint Wiki Information
- Next by thread: Re: Sharepoint Wiki Information
- Index(es):
Relevant Pages
|
