I think a Wi Ki is hugely superior to a Web Log for a team (Wiki For Collaboration Ware).
I even think it's superior for an individual thinker (Thinking Space). I'd like to see every "smart" blogger actually use a Wiki Weblog. What can increase the penetration of that idea?
Provide Web Log-like view. Already done here (2002), others are playing with similar ideas.
Change initial perceived weirdness: (done May2003)
Question Mark to signal opportunity to create a new node. I'm going to try switching to square brackets for that - I think Va Nilla already does that.
Get RSS code in all the popular Wiki Engines (done May2003).
(Probably wouldn't include all content, but maybe forward links and local Back Links once they're cached.) Also should probably use Expanding Wiki Words.
Have some other context/structure cues on the Front Page along with that current-blog view. I think this best by Transclus Ion of specific pages (like Blog Roll). (done Jun'03)
Cache local Back Links list at bottom of each page, to help people find more related content. Maybe cache forward links as well for various purposes.
Provide some sense of place/structure/context for a single wiki page (blogs actually don't do this well).
ZWiki offers Hierarchal Structure - see top-left of each page
visual tools - Touch Graph (works now), Idea Graph (Danny's working on it). Once caching Back Links and forward links, could use WikiWikiWeb:VisualTour code to pop up local map.
Track Back support? Offsite Back Links?
How important is availability of "visual editor" (Ms IE DHTML control) vs simple text markup? Some say it's key, but I think I saw a survey recently saying that most people don't use that tool (though it might not have been very representative - but again, my goal isn't necessarily to get every single blogger switched over).
More Wiki Standards convergence to encourage Wiki Web. (aka Sister Sites requires Smashed Together Words)
Out Lining tools
- editing
via Rich Client
Structured Writing style?
reading - Active Renderer
Share info about Wiki Farms. Run my own Wiki Farm ASP. Give away a few accounts.
Work with a Wiki Engine that doesn't require a whole Application Server underneath it, to improve installation ease and documentation. Or maybe just track other people's comments about that issue for various engines, and summarize recommendations. (complement to running Wiki Farm)
Change entire architecture - run as local Rich Client/Desktop Server (OSAF/Chandler?), then render to static pages.
Advantages: easier installation; cheaper hosting; faster delivery. Might actually make it easier to graft on dynamic elements from Web Log universe - Track Back, etc.
- Disadvantages: harder to upgrade code. Hard to work from multiple machines (work vs home). Lose search functionality. Can't allow appending comments to pages, much less editing.
(more....?)
<b>see TooFewWiki</b> --2004/02/05 23:04 GMT<br> Argues toward a future with One Wiki Per Topic. I think more in terms of One Wiki Per Person, with these getting connected via Inter Wiki Map and Sister Sites into One Wiki Per Group...