Similar to the kitchensink example, Vineet Renoylds--a key Arquillian contributor--has put together a full stack Java EE 6 example named Galleria. The best part is that it uses Arquillian all over.
The Java EE 6-Galleria is a demo application demonstrating the use of JSF 2.0 and JPA 2.0 in a Java EE project using Domain Driven Design. It was written to serve as a showpiece for domain driven design in Java EE 6. The domain model of the application is not anemic, and is constituted of JPA entities. The entities are then used in session EJBs that act as the application layer. JSF facelets are used in the presentation tier, using Mojarra and PrimeFaces. The project seeks to achieve comprehensive coverage through the use of both unit and integration tests, written in JUnit 4. The unit and integration tests for EJBs and the domain model rely on the EJB 3.1 container API. The integration tests for the presentation layer relies on the Arquillian project and its Drone extension (for execution of Selenium tests).
Galleria Source Code (hosted on BitBucket)
At the moment it lacks a tutorial. Vineet said he'll be working on it soon, but it could be something that we could help with as it will be a win-win.
It's also configured to use GlassFish. We can help him fix that bug j/k But it would be good to have multiple container support.
Ah well, I'll consider that. Now that I've started working on the wiki, the difference in wiki engines might make a transition more difficult. BitBucket uses Creole, unlike GitHub. But then again, it might be better to have all the docs & guides on a separate site (on OpenShift perhaps), just like Arquillian - http://arqpreview-alrubinger.rhcloud.com/
I'll start by saying that it doesn't matter to me where it's hosted. It took me no more time to check it out and start playing with it then if it were on github. It's DVCS, that's the important part. So I'd say choose what you think is best for you.
For completeness, the Github wiki does support Creole. In fact, it supports every major lightweight markup language thanks to the github-markup and github-gollum template abstraction libraries (markup is the library, gollum is the editor). You just select your markup in the menu above the upper right hand corner of the text area when you are editing.
I agree, though, that the guides should be hosted on a separate site to bring them all together. That's a problem we haven't yet completely solved...but that shouldn't get in the way of writing up the tutorials. Moving information around is far easier than writing it
Btw, the wiki is looking good!!! I can't wait to dive into it! For the audience, here's the link:
My initial statement needs to be updated, you do have a tutorial in progress. So it's us that could contribute to your effort
Here's an example of the Creole markup in a Github wiki page (a gist and a repo wiki use the same editor):
Note that Github does not support syntax highlighting in any markup language other than Markdown. There's an open ticket for that.