At the moment the project has to be used as a full-blown application that uses ICEfaces for the "frontend" and AppFuse for the "backend". It is based on the basic jsf archetype and not a separate presentation layer that can be used instead of something else.
We are in the prototype phase that shows that it works. But, there's still a lot to do.
At the moment I try to realize a kind of application core that can be used to implement AppFuse/ICEfaces applications. But, it is already clear that the current AppFuse implementation needs adaptations to get an optimal integration. Before, I discuss this with Matt in detail I use the programming examples of my forthcomming book about ICEfaces to check how such a core has to be designed.
Nevertheless, you can study how ICEfaces is integrated and take the specific parts into your project.
I deleted most of the AJAX stuff and sitemesh, exchanged the Facelets support and added ICEfaces 1.7.2.SP1. Skinning is done by Facelets/ICEfaces now. Login still exists the rest is not really usable. ICEfaces is using MyFaces and we have support for Tomahawk (although not recommended when skinning is important; I've to check if it is possible to get certain similarities in presentation in the future).