Packt Publishingrecently released their new book “ Managing eZ Publish Web Content Management Projects” written by Martin Bauerfrom designIT.

I just went through it and this is the first book ever written about managing content management projects in general and using eZ Publishin particular. There’s a lot of technical documentationand end user documentationabout eZ Publish, but there has not been any documentation for project managersbesides the more general project management literature.

This book contains information on all phases in a typical eZ Publish projects life cycle. From gathering requirements, writing a project brief, planning a workshop with the client, get to the right estimates, writing the requirement specification, managing risk and find the right pricing. To managing the production using concepts from agile development, managing the information architecture with content modeling, testing, training, maintainance and support.

The nice thing about this book is that it’s not technical. It’s closely related to eZ Publish, but it also goes a far way on the content management part.

If you are a project manager responsible for any eZ Publish projects in your organization you should definitely read through this book. Developers, designers and end users can look somewhere else. However, developers and project managers work tightly together and need to understand each other. So your job as a developer is to continuously educate your project manager to understand your world - the first thing you can do is buying him/her this book

So, a last tip from me: Most real life content management projects is a job for “The Three Musketeers” (the designer, the developerand the project manager).

• You need a solid interaction designer to create all the nice looking web interface so both the client and user gets happy (no one likes a bad interface even though the back-end solution is fantastic).
• You need a good developer that now how to slice the web design, know the eZ Publish product, the template language and how to create custom extensions.
• And you need the project manager to manage everything described in this book.

This JavaScript client library allows you to make Facebook API calls from any web site and makes it easy to create Ajax Facebook applications. Since the library does not require any server-side code on your server, you can now create a Facebook application that can be hosted on any web site that serves static HTML. An application that uses this client library should be registered as an iframe type. This applies to either iframe Facebook apps that users access through the Facebook web site or apps that users access directly on the app’s own web sites. Almost all Facebook APIs are supported.

A simple command-line tool to create the folders and helper files for a new JavaScript project/library. As a bonus, you can quickly create a website to promote your project.

When you start a new JavaScript library, how do you layout the source files, the tests, the distribution files? Do you have support scripts to generate distributions from source files? Run your JavaScript unit tests? Generators to create new unit test HTMLfiles?

JSJaC is a jabber/XMPP client library written in JavaScript to ease implementation of web based jabber/XMPP clients. For communication with a jabber server it needs to support either HTTP Pollingor XMPP Over BOSH(formerly known as HTTP Binding). JSJaC has an object oriented design which should be quite easy to use. Communication is done by using the XML HTTP Request objectalso refered to as AJAX technology. Your browser must support this.

Using Caja, web apps can safely allow scripts in third party content.
The computer industry has only one significant success enabling documents to carry active content safely: scripts in web pages. Normal users regularly browse untrusted sites with Javascript turned on. Modulo browser bugs and phishing, they mostly remain safe. But even though web apps build on this success, they fail to provide its power. Web apps generally remove scripts from third party content, reducing content to passive data. Examples include webmail, groups, blogs, chat, docs and spreadsheets, wikis, and more.
Were scripts in an object-capability language, web apps could provide active content safely, simply, and flexibly. Surprisingly, this is possible within existing web standards. Caja represents our discovery that a subset of Javascript is an object-capability language

What is XSTM?

XSTMis made of three projects. The Java implementation is called JSTMand is the base from which the other versions are derived. An adapted version made with Luciano, the author of GWM , is available for GWT . It allowsthis library to be used in a browser. NSTM is a .NET port based on IKVM.

All implementations are compatible with each other so object replication can take place e.g. between a Java server and a .NET Smart Client.

jQuery UI is a set of themable widgets and interactions, built on top of the jQuery JavaScript Library, that you can use to build highly interactive web applications.