See also ScoopMeetsTWiki, and the CMS/Weblog/newslog mini-overview/muse, ContentManagementSystem - the "we use iManage. Not different from other CMSs... rigid, hierarchical, clunky, expensive. ... Once TWiki gets a prettier face, it's all over for those US$500,000 piece-o-crap CMS systems!" (DavidWeller 26 Nov 2001) comment there was interesting, but the topic stopped there. Also, RichardDonkin's 21 Jan 2002, "applications sell TWiki - if somebody finds a 'killer app' for TWiki in a particular organisation, that can really move it forward" hits the same point from an (apparently) different context in HowToGetInternalBuyInForTWiki.

Other CMS/newslog/weblog programs are considering Wikis as well. Why? Where, if anywhere, does this lead? And what if, instead of simply slicker templates, TWiki distribbed with a few packaged "apps" - simple sets of config instructions for standard features - searches, formatting, forms, template mods, certain plugins and add-ons, even w/o any design elements - that would each turn a single web or whole site into "one thing" or "another", as opposed to the blank slate releases of now? What would happen to TWiki then, out there in, say, the general business world, for a start?