Tags:
extract_doc1Add my vote for this tag create new tag
, view all tags

Collaboration Situations

This open list describes all types of collaboration/interactive communication situations that're powered by TWiki. Feel free to add your own...


Programming Dev / Fan Site (2)

  1. My own effort to create a programming language.
    Currently, this is a single writer (myself) and many readers (who occasionally insert a question or a note).
  2. A friend of mine is setting up a fan site.
    In his set-up, people will be either administrators, project leaders, or fans.
    Administrators will have shell access and keep the site running.
    Project leaders will be responsible for specific Webs and get some information long before the fans see them (to avoid spoiling the fun).
    Fans will be free to see most content and edit some of the content.

-- JoachimDurchholz - 28 Dec 2001


Online Biz / DJ Timeline / Intranet (3)

Using TWiki for about a year and a half, I've adapted it, with varying degrees of success, mainly to three quite different situations:

  • virtual office platform for a Net-based biz research/consulting service
    • on the biz side, the usual Web products/services/about content
    • on the client value-added side, a set of resource webs: basic business tools; research/reference resources; news/trends tracking
    • design was a combination of locked TWiki HTML gateway pages, and simpler TWiki collab pages for interactive areas.
      • simple look, recognizably TWiki, but with a lot of heavier HTML in the templates (pretty detailed, nested table toolbars; with embedded graphic buttons; for DHTML sliding menus for nav; etc
      • created HTML externally - multi-column tables, multiple forms, etc) and pasted in for many gateway/special purpose pages
    • Nothing very difficult. Most of this was before the heavier new TWiki features, like WebForms, the new templates system, plugins... But it worked fine.
    • never launched service

  • a visitor-interactive DJ/dance/electronic music timeline
    • kind of in the http://wikipedia.com knowledge builder mode
    • traces the history of house and techno, broken out by style, from '80s to '95; very concise copy, references to key artists/tracks, tiny logos & pics
    • had it online in two static HTML formats; originally from print mag
    • started transfer to TWiki, intend to open for updates
    • didn't plan it for TWiki, slapped up straight manual crosslinking : one topic per music genre+year, ex: AcidHouse1993. Results rather dull, visually/functionally. But TWiki is perfect, with a plan.

  • all-purpose intranet for indie music/video label/production company
    • "small" company: one NYC office, staff of a dozen or so, couple of close subcontractors (extranet), loose net of freelancers; few million annual revenue
    • MS small biz environment: NT server, Office 2000, a few Macs in...art dept! Commercial DSL to Net, collab by email - Outlook/Exchange
    • my role is biz dev, but getting organized group communication and reporting was essential, to me, and to owners: DIY
    • decided on TWiki mainly 'cause it's as easy to use as email
    • standard install, with stylesheets, new colors, etc, using TWiki notation heads/TOC, loaded templates for project planning, reports, checklists: enter title in input field, hit create (like Codev new bug report)
    • using since 03-Dec-2001, served off Linux/Apache virtual host for now (ie: a Web login for users)
    • for this version of a corporate intranet - where collab IS a big part: core planning for pay-per-view events, record releases, etc - a LOT of customization is required. To date, could be brilliant with lots of tweaks, including look. Most people now on pause - not rejected, not really used, either

-- MikeMannix - 28 Dec 2001

UPDATE: Totally reorganized over holidays. Started minimal, let people fill in. Now, each web home is a structure TOC in HTML table 8-10 headings, 30+ ttl links per home, four webs + help. Linked to WebCalendar from toolbars.

-- MikeMannix - 06 Jan 2002


Gaming (Lotus Notes Conversion)

We have been converting a public 'gaming, and general nonsense' website from LotusNotes to Twiki.

You can see the original website at http://evem.org.au or the new TWiki development site at http://www2.evem.org.au . Click on an article to see the keyword navigation at the top of each article (this is created automaticaly by our plugin). If the development site is dead it's because we are working on it...

-- AdrianLynch - 03 Jan 2002 (excerpt from: TaggingRelatedTopics)


Help system for web-based (CGI) application

Our CGI application is called YMD. I created YMDhelp web on our site. Perl scripts generate HTML pages, which has Help links, pointing to TWiki pages in YMDhelp web. Users felt confused by all options in "classic" view template, so I created HELP skin which does not allow even edit a page or any other "advanced" features. HELP skin has link "Developers" to change skin for current topic. But even developer's skin is much simpler than "classic" Twiki skin. HELP is default skin for whole YMDhelp web. See live at SimplerDefaultTemplates#SimpleSkinDone.

I added CommentPlugin to allow users to add comments to any page. Comment is not authorised, so even non-registered user can post question, but only authorised users can edit page (and answer questions).

I like that I have possibility to test our app from home and fix documentation, and users will have immediately new fixed version of docs. (not that I am am doing that - I play with TWiki at home smile )

-- PeterMasiar - 08 Mar 2002


Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r5 - 2008-09-14 - 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.