Latest Posts

Popular Posts [+]

Archives [+]

Categories [+]

Authors [+]

Follow us on Twitter

#German #Webinar: Enterprise2.0 with CQ5. Register now http://day.com/CQ5Enterprise20 #CMS #Enterprise2.0

4 days ago

RT @trieloff: We improved the chart rendering for bar and line charts in #CQ53 http://bit.ly/azfzBK #featureoftheday

7 days ago

RT @davidnuescheler: Congrats to @rmcveigh / Oracle and Peeter Piegaze / Day to be elected unanimously as Secretary of the #CMIS TC

11 days ago

RT @trieloff: CQ5 DAM's Mosaic Lens allows easy asset browsing http://bit.ly/dxGdLK #featureoftheday #CQ53

11 days ago

Free Sept 1 webinar: How Chicago's Metra evolved its online presence. http://www.day.com/metrarailoncq5

12 days ago

Entries filed under 'cms'

    Posted by Michael Marth JUN 10, 2010

    Posted in cms, everything is content and modelling Comments 2

    Comment on content and CMSs

    Last week I have uploaded a Twitter clone application to Day's Package Share. The application's content package not only contains some sample content and the jsp files with the application code. It also includes sample users and their respective access rights on different JCR nodes. Putting all this information in one content package is possible (and even simple) because users, ACLs etc are stored in the content repository as JCR nodes.

    The experience of putting together this package nicely reminded me of the power of the concept of storing all of a a web application's artefacts in the content repository - which can be considered the technical implementation of Day's mantra "everything is content".

    Classically, the image of web content management systems one has in mind looks something like this:

    /content/ddc/blog/2010/06/comment_on_contenta/jcr:content/par/image_0/file

    Content is the input and a web page is the end result of some rendering process. There is nothing wrong with that image, but considering "everything is content" an alternative prototypical image of a CMS came to my mind:

    /content/ddc/blog/2010/06/comment_on_contenta/jcr:content/par/image_1/file

    A web content management system's repository is the place to store and manage all aspects that make up your web site. The web page is not only the end result, but also the source.

    Posted by Michael Marth MAR 12, 2010

    Posted in cms Comments 6

    The fat years are over

    When you look at the technology options one has for a CMS authoring interface there are two big camps: the web UI and the fat client (be it a Java client, .net or similar). The relative pros and cons of these two technology choices are usually described along these lines

    • web clients are easy to deploy whereas fat clients are not
    • on the other hand, fat clients provide a richer user experience and better usability overall.

    Consequently, fat clients are often suggested as the preferable solution for so-called power users whereas web clients are supposed to be the right thing for occasional CMS users.

    Well, these considerations have been around in the CMS community for about 10 years and I have not seen a lot of discussion about them. But I think they are not true anymore. The world has moved on and browser-based user interfaces have not only caught up with fat clients in terms of usability - I think they are even about to provide a better user experience.

    This is part of a very large trend in the computer industry: applications that were once desktop-based move into the browser with the primary examples being GMail or Google Docs. This trend has been facilitated by vast increases in browser performance and better widget libraries like JQuery or Ext. These improvements have made it technically possible to implement user interfaces that are as rich as desktop applications.  Drag-and-drop, tree widgets, responsiveness of the UI - most of what was once thought to be the desktop app's advantage now also exists in the browser.

    However, there is more to this trend: I, for example, have grown completely accustomed to having all my productivity apps within the browser. And because I spend most of my time within the browser it is the browser's infrastructure that defines "convenient" for me, be it password management, download- and upload-behaviour, the browser extensions I have come to rely upon or simply the fact the the browser is always running anyway.

    In my case the increasing tendency to use browser-based apps rather than desktop-based ones even goes out to the choice of my IDE for component development (arguably the most power-user-y thing to do). Day offers the Eclipse-based CRXDE as well as the browser-based CRXDELite and I find myself starting to the latter more and more often - because it is often simply more convenient.

    So, coming back to CMS authoring interfaces: In my opinion the fat client's deployment hassles are not compensated by usability anymore. Maybe, it is time for the CMS community to revisit this topic.

    Posted by David Nuescheler DEC 02, 2009

    Posted in cms and cq5 Comment 1

    Top 10 Features in the Upcoming CQ 5.3 Release

    Here is a short presentation with my personal top ten features in our upcoming release. Of course, this would ideally be accompanied by short fast paced demos, so if you are interested in getting personalized demo or a video, please reach out to us.

    What's new in CQ 5.3? Top 10 features.
    View more documents from David Nuescheler.

    Posted by Greg Klebus NOV 11, 2009

    Posted in cms, cq and ignite Add comment

    Ignite Chicago

    After the Ignite in Zurich, there came Ignite in Chicago, where our American customers, prospects, partners, and Day staff met to share information, experiences, to network, and simply have a very good time. The event itself was slightly bigger than the event in Zurich, both in terms of number of participants and available room.


    Ignite was hosted by Day customers, in more than one way: by the City of Chicago itself, and by the grand Intercontinental Hotel, of the IHG Group, on Chicago's famous shopping avenue, the Magnificent Mile.


    Again, we had a lot of great presentations, panels, Q&A sessions, as well as informal chats. And the Foreigner concert at the end was the icing on the cake.


    Be sure to check out the conference hashtag was #dayignite and here are some Ignite pictures on Flickr, with lots of new coverage from Chicago:

    Looking forward to next year's Day Customer Summit!

    Posted by David Nuescheler NOV 05, 2009

    Posted in cms, cq5 and wcm Add comment

    JBoye Presentation: WCM Trends for 2010

    Today I had the opportunity to speak at the JBoye conference in Aarhus. It was a pleasure as every year since the audience and speakers really constitutes a who-is-who of WCM visionaries and insiders. I am definitely looking forward to coming back next year.

    JBoye Presentation: WCM Trends for 2010
    View more documents from David Nuescheler.