We are looking at including journaling capabilities in our MediaWiki
installation because:
A) we would like users to be able to use the same editing skill-set for both
personal- and community-authorship documents
B) we would like wiki entries and blog entries to be able to cross-refer
with wiki-like ease (both via explicit links and via
trackback/what-links-here automation).
We made a list of the most-desired blog functionality:
1) Post
2) Tag (author-specific or community?)
3) Display by date
4) RSS feed (by date, by tag)
5) Discuss (comments on posts)
6) Trackback (what links here)
7) Ping Receive/send (join the blogosphere)
8) full-text search
9) Monitor (watchlist, revert)
10) Notify (email when a new comment is added)
Given MediaWki 1.5, we believe we can do 1, 2, 4, 5, 6, 8, 9, and 10 in some
form pretty much out of the box or with existing extensions. 3 doesn't seem
like a lot of code. 7 is obviously a couple of extensions; it's not a
crucial need for us at first, anyway.
As always, these decisions should be based on requirements and cost-benefit
analysis.
-- Joshua
On 8/15/05 7:56 AM, "Brian Ross" <brianross(a)minorleaguenews.com> wrote:
Tinker stick to shoes. If you want a weblog, use a
calendar-driven system
like Radio (
radio.userland.com), not Wiki. We use both for different
purposes. You won't have to recatalog and build anything using Radio for the
purpose. If you want Wiki features, try using Wiki for the component of your
site for which it was intended. You can use simple URL links between the two
apps to get a larger site look and feel.