Tags:
classification1Add my vote for this tag competition1Add my vote for this tag version_control1Add my vote for this tag create new tag
, view all tags

TWiki & Content Management Systems (CMS)

How structured can/should a T/Wiki get?

Content Management Systems - Web portals - are the other end of the the spectrum from Wikis. Like Wikis, they're collaborative, user-driven, highly flexible, and serve as a content infrastructure. Unlike freeform Wikis, CMS flexibility comes from being highly structured - content is so modularized that a great degree of flexibility results.

Interesting is Scoop:

  • "The style of weblogs is very linear - it lends itself well to news, diaries and interesting findings on the web, but it is less suitable for long-term, goal-oriented discussion of a subject, or collaborative content creation. The integration of a wiki into the Scoop codebase would make it possible to use a Scoop site for both purposes."

This succinctly proposes an obvious TWiki dev consideration, a variation on "build or buy": does it at some point become more practical - if not the only alternative - to blend TWiki with separate tools, rather than build in functionality...

Related topics: TWikiDeployment

-- MikeMannix - 04 Oct 2001

We use iManage where I work. Not different from other CMSs... rigid, hierarchical, clunky, expensive. Yup, that just about summarizes them smile Really, I'm trying to promote TWiki as our "internal" knowledge collaboration site and our CMS system as our "client-facing" portal/content tool (we're a consulting company). I think it will work very well. Once TWiki gets a prettier face, it's all over for those US$500,000 pice-o-crap CMS systems!

-- DavidWeller - 26 Nov 2001

I dunno how much confidentiality applies in your situation, but I, for one, and no doubt others, am interested in your progress, and in...collaborating, in any useful way. I'm in a perfect live test situation, deploying TWiki as intranet from scratch. I've put a couple notes here and there, but I'll gather and post as a kind of dev log. There's no NDA on my end, and I don't think custom programming is required, it's all working out UI (design elements) and usability of basic features - and, of course, making it feel USEFUL to all who have to fully accept it, reception to CEO, to make it work. So, I can share ideas and observations no problem.

There are a few notes on this project in CollaborationSituations.

-- MikeMannix - 28 Dec 2001

I'm curious about the commercial CMSs - are they similar in concept to the OpenSource WebLogs, or do they offer a richer model? I have a hard time seeing a WebLog as a real CMS, given that they impose a very specific time-sequenced (i.e. weblog) structure on the site.

-- RichardDonkin - 15 Feb 2002

Just discovered http://www.opensourcecms.com/ - "This site was created with one goal in mind. To give you the opportunity to "try out" some of the best open source software systems in the world. You are free to be the administrator of any site here, allowing you to decide which system best suits your needs."

Seems to be restricted to php based systems, and doesn't include any wikis but still worth a gander.

-- MattWilkie - 12 Dec 2002

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r8 - 2008-09-15 - TWikiJanitor
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.