Daisy: CMS or Wiki?

Copyright (c) 2007 Peter Dykstra 1

Copyright (c) 2007 Peter Dykstra

Daisy: CMS or Wiki? Open Source Case Study

Peter [email protected]

STC-Philadelphia Metro Chapter Annual Conference

March 17, 2007


What’s a Wiki?

First introduced in 1995Server-based software, allows discussion / collaborationDistinguish

WikiBlogForum



Original Definition

“The simplest online database that could possibly work.”

- Ward Cunningham(inventor)

Source: www.wiki.org


Wiki characteristics

Allow users to freely create and edit Web contentUse any Web browserSimple text syntax (HTML not required)Cross links

(source: www.wiki.org)



Effect of Wikis

Powerful and subtle effects of Open EditingEveryday users can edit any pageEncourages democratic usePromotes content composition by nontechnical users

(source: www.wiki.org)


Compare: Wiki vs CMS

WikiBottom-up approach to structure and navigationAbout empowering users

CMS (Content Management System)Top down approval / coordinationAbout managing content efficiently following a set of rules



Similarities

Can use the same technologyWikis require SOME central managementSimilar user needs

Edit rightsEase of use


Differences

Social and governance modelDEGREE of control -- continuumNeed to control / identify the source / speak with one voice?Specialized publishing roles?



Original WikisSimple storage, files stored in server directoriesOne copy, no versioningIssues:

SprawlHard to navigate random structuresNo process for keeping text updatedNo edit history / tracking


Newer Wikis

Thousands of pagesWikipedia English version = 1,688,000+ articles (3/16/07)

More formal governance modelsDatabase back endsVersioning, tracking, and rollbackSpecialized administrator rolesStart to look more like a CMS



Introducing DaisyCMS-based WikiHigh-end featuresOpen Source / Standards-basedFree to use and distribute (“Apache-style”license) Some tech required


Where’s it from?Outerthought

Small co (3-4 developers) in BelgiumGovernment fundingConnections to Apache Software Foundation

Two levels of supportOpen Source community (free)Outerthought Support contract ($)



Apache Software Foundation

Known for Apache Web browserSupported by major software cos

Sun, IBM, HP, etc.Open licensing modelJava-basedWeb / XML / XSL focus


Daisy Technology

Integrates Apache componentsCocoon Web publishing frameworkLucene search engineMessaging

Uses MySQL Open Source databaseAdds a content repository and editor



Two main parts of Daisy

Front end: Daisy WikiXML-based publishingBrowser-based wysiwyg editor for html

Back-end: CMS repository“Daisy HTML” document formatStore other file as attachments

Extensible (XSL, CSS, JavaScript, Java)


Daisy architecture

Repository WikiAPI



Daisy architecture

Repository WikiAPI

Web site(s)


Repository

Single ‘big bag’ of documentsVersioned documents / diffsMetadata as document fieldsDefinable document typesAll communication via API



Repository features

Two main document formats‘Daisy’ HTML subsetAttachments

Full-text search (html, doc, xls, pdf, txt)Authorization/RolesQuery languageSubscribe to event notification


Daisy Wiki

Standalone applicationWysiwyg HTML editorSupports multiple “sites” from one repository, based on metadataVirtual document hierarchies derived from metadata + rulesBook publishingBuilt using the Cocoon framework



What’s Cocoon?

Apache projectWeb publishing / application frameworkProvides XML processing on the serverSupports the WikiCan be used to build Web sites using the repository


Sample Cocoon processing

Source files

(Daisy repository)

Sitemap

XSL Stylesheetlibrary

1. User enters request for “sample.html”.

2 Sitemap sees “*.html” …

Match=“*.html”Sample.xml

3. …gets “sample.xml”…

4. …transforms it using xml2html.xsl…

5. …and sends “sample.html” back to the user.

A sample pageThis content for this page is in an xml file. The html file doesn’t exist until someone asks for it.

The user never sees the xml.

xml2html.xsl

http://www.site.com/sample.html



Goal: “Separation of Concerns”

Cocoon’s architecture separates

Program logic ContentVisual style / brandingSite management

so they can be managed independently


Official Daisy site (shows the Daisy Wiki)



Daisy Wiki (Modified styles)


Daisy Wiki



Daisy Wiki


Daisy Wiki



Our Experience


Our Experience

Setup ConfigurationInfrastructureAuthor trainingSample projectUser responseOpen issues



Set up (test environment)

Install on a standalone PCDownload and install JAVADownload and install MySQLDownload and configure DaisyStart upEstimated time: 1-3 hours


Configuration

Modify logo, fonts, colors Define desired

Document typesFields and field values (metadata)

Sample documentsSet up “Collection” for each work groupSet up “Site” for each content area



Infrastructure

Two stages (after test install on a PC)Pilot server installation with IT groupProduction server installation

LDAP directoryBackups


Author training

Appointed one editor / trainerRequires some understanding of HTML

Created company-specific document typesOne-on-one training sessions with authorsSupport for problem resolution



Sample project

Developer’s LibraryArchitecture documentation for development groupWiki style documentsPDF / Word / Visio, etc


ResultsEnthusiastic sponsorship by technical managersParticipation by content owners

With editorial support: Full participationAs authors: Limited participation (slowly expanding)

Built library of 1500+ documents across 10+ teams High level of awareness/use by ‘consumers’Easy browse/search is key factor Rated as successful at building common technical understanding



AssessmentOn the one hand

Documents are centrally accessibleSite structure is intuitiveTools are accessible, easy-to-useWikis are cool

On the other handDoc creation/editing is still by a limited groupSome HTML knowledge requiredEditorial support is still important


General experience

Easy to train interested authors who have basic Web/HTML understandingAuthors can manage contentSome editing was needed Main success factor is ability to write clearly



Lessons


Open Source Lessons

Open Source software can be powerful and robustIt provides a hands-on way to learn about CMS Use in the right business context can provide significant benefitsOrganizational learning curveOne size doesn’t fit all projects



Software is not the solution

An Enterprise CMS system has to be integrated into the workflow of an organization

Clear goals and requirementsDefined rolesNeeds to present itself differently to different users


Content issues vary

Very different requirements and success criteria for

Internal Wiki / Intranet External Web siteOffice document management



ConclusionsOpen Source may be the right choice for some

Robust core featuresFlexible, extensibleParticipate in the communityNo license fees

Rough edgesRequires expertise

Information ArchitectureInfrastructure managementApplication configuration


Conclusions

Not freeRequires business and technical

SkillsTime

Development and support depend on an external communityFeature gaps may require development



Vendors offer

GuidanceBroad and deep experienceRicher feature setsSupport


Daisy Strengths

Integration of industrial strength components Versioned document modelSeparation of concerns

visual designcontent creation/editingsite logic

Repository architectureOpen standards-based design



Recommendations

Good learning projectReady for medium-size applications Good for managing technical documentsRequires fairly technical orientation


Links / ContactsOuterthought / Daisy

http://outerthought.org/site/index.htmlhttp://cocoondev.org/daisy/index.html

Cocoonhttp://cocoon.apache.org/

Forresthttp://forrest.apache.org/

[email protected]

Daisy: CMS or Wiki?

Technology

Transcript of Daisy: CMS or Wiki?