• Save
Using a Wiki as an Organization Portal (at TriXML2006)
Upcoming SlideShare
Loading in...5
×
 

Using a Wiki as an Organization Portal (at TriXML2006)

on

  • 4,701 views

This is a presentation given by Rick Sapir and Bill Albing (of KeyContent.org) about their use of a wiki as an organization web portal. This was given at the TriXML 2006 conference, in Raleigh, NC.

This is a presentation given by Rick Sapir and Bill Albing (of KeyContent.org) about their use of a wiki as an organization web portal. This was given at the TriXML 2006 conference, in Raleigh, NC.

Statistics

Views

Total Views
4,701
Views on SlideShare
4,698
Embed Views
3

Actions

Likes
5
Downloads
0
Comments
0

3 Embeds 3

http://www.slideshare.net 1
http://ricksapir.com 1
http://speakers.keycontent.org 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Using a Wiki as an Organization Portal (at TriXML2006) Using a Wiki as an Organization Portal (at TriXML2006) Presentation Transcript

    • Using a Wiki as an Organization Portal for Tri-XML 2006 by Rick Sapir and Bill Albing
    • Outline
      • Pick a more social portal
      • Select a wiki-based CMS
      • Develop a full-featured portal
      • Learn from our implementation
      • Conclusions
      • Demos
      • Contact Us
    • Pick a more social portal
      • Signs that you've outgrown your present web site
      • Reasons to "Go Social" (Where is your organization going?)
      • Is Web 2.0 for real ?!
    • Signs of outgrowing
      • Too many pages not searchable (or search databases not connected)
      • Too many requests on IT dept or on Web manager by content developers
      • No sense of ownership of relevant parts of Web site
      • Other groups developing their own wiki or blog or other splinters
    • Reasons to "Go Social"
      • Q: Where is your organization going?
      • Internal groups need more collaboration
      • More groups, both internal and external
      • Economy of (social) scale
      • Innovative groups need dynamic tool(s)
    • Is Web 2.0 for real ?!
      • Yes, Web 2.0 is arriving, piecemeal
      • Yes, but only as real as you make it
      • The rest of the world is discovering it (and isn't going to wait for you)
      • Some are already planning Web 3.0, etc.
    • Select a wiki-based CMS
      • Decision tree looks something like:
      • What are the options?
      • What is a wiki?
      • What is TikiWiki?
    • What are the options?
      • SharePoint Services (doc based)
      • Wiki-based CMS packaged
      • More complicated virtual community
      • Stand-alone collab tools (Gliffy, Jot, Google, Writeboard, etc.)
    • What is a wiki?
      • From user point of view:
        • Ability to edit content on the site
        • Edit from Web browser
      • From the admin point of view:
        • More installation and setup
        • But freedom as package handles admin
        • Users manage content
        • User admin easy; version control etc.
    • What is TikiWiki?
      • Database stores all the information (settings, options, etc.)
      • Application in PHP with "business logic"
      • Presentation layer uses Smarty, a template engine
    • TikiWiki layers diagram
    • Develop full-featured portals
      • Tools we picked
      • Create "Key" areas
      • Overcome user fear
      • Define editorial control
      • Handle installation
      • Handle customization, choose theme
      • Handle wiki package updates
      • Fight spam
    • Tools we picked
      • Articles (wiki pages)
      • Sample page (sandbox)
      • Graphics/images
      • Syndicating other sites' feeds
      • Blogs
      • Resources (links) (Categorization key)
      • Events / Calendar
      • Left Menu Navigation
      • Search
    • Create "Key" areas
      • Articles as wikis (Key Articles)
      • Calendar events (Key Events)
      • Resource links (Key Resources)
      • Blog (right now just one, but in future, each user)
    • Visual example
    • Edit article
    • Overcome user fear
      • Some users new to wiki
      • Some users new to collaboration
      • Some users new to our site
      • Some users want ownership/control
    • Define editorial control
      • Collaboration requires new editorial process
      • Several stages – some articles reviewed, some auto accepted
      • As site grows, assign editors to subsections of content areas
    • Handle installation
      • Install TikiWiki
      • Configure TikiWiki / choose theme
      • Choose which tools
      • Differentiate
      • Branding
    • Handle customization
      • Customize only at presentation level
      • Choose theme
      • Avoid customizing business logic
      • Keep backups and use test area
    • Handle wiki package updates
      • TikiWiki comes out with update every two months or so
      • Keep in touch w/ developer community don't be afraid of submitting updates
      • Always test update in test area before making public / live
    • Fight spam
      • As more social, spam is an issue
      • Article requests, event entry, etc. all user inputs can result in spam
      • Filters possible but not built in
    • Learn from our implementation
      • Accept wikis' limitations
      • Maximize wiki's advantages
      • Who else can use this?
    • Accept limitations of wiki
      • Package is not all things to everyone
      • Not HTML
      • Not WYSIWYG
      • No standard wiki syntax
      • Give up some control of admin Give up some control of content
    • Maximize wiki advantages
      • Create new pages on-the-fly
      • ANYONE can edit with only a browser
      • Automated admin
      • More direct ownership of content
    • Who else can use this?
      • Any group!
      • Local chapters of professional associations and user groups (Tri-XML, STC Chapters)
      • Non-profit social agencies etc.
      • Intranet inside a corporation
    • Conclusions
      • Wikis are powerful packages
      • Social software gaining acceptance
      • Wikipedia and KeyContent are success
      • You can use wiki
    • Contact us
      • Bill Albing [email_address]
      • Rick Sapir [email_address]
      • www.keycontent.org
      • See the complete article and slide show at: www.keycontent.org/tiki-index.php?page=Wiki-based%20Portal