Wikis are a great software tool for collaboratively creating and editing
content. They seem to be an obvious choice for building a community Web
infrastructure. Yet they have serious drawbacks that made JBoss.org choose a
Content Management System (CMS) instead of a Wiki to build its new community
website.
Managing Content of High-Traffic Community Sites
JBoss.org's website currently serves 20 million page views per month and
hosts over 40 community projects within that website. Each project area has a
navigation menu on the left and a content area on the right. Some projects
need more pages than others because of their project structure.
JBoss.org currently uses an in-house system they developed, but wanted to
focus on adding value for the more than 40 software projects it hosts,
instead of maintaining a self-made CMS. Initially in April 2008, JBoss.org
evaluated W... (more)
On Wednesday Adobe announced it was going to buy Day Software, another WCM
manufacturer based in Basel, Switzerland, who uses the same technology
foundation as Magnolia. As an initiator of the JCR standard and main
contributor to Jackrabbit (the JCR reference implementation), Day is
certainly important for the JCR ecosystem.
Let's have a look at the possible implications of the deal for Magnolia.
Adobe bought Omniture not even a year ago for 1.2B$, which was/is the leader
in web analytics. With Day's CQ (their CMS), Adobe now has the final part in
their portfolio to create, analy... (more)